We are releasing Dnspooq - 7 vulnerabilities in dnsmasq, and open source DNS forwarder used in major Linux distributions and by dozens of vendors
https://t.co/IGUcbozn3A
I found some design and implementation flaws in Wi-Fi again. All Wi-Fi devices are affected. It was a long ~9 months embargo, over this time a lot of info has been collected and that info now available at https://t.co/nAQtK9XY0R
Forescout & @JSOF18 research disclose NAME:WRECK - 9 new DNS #vulnerabilities affecting popular TCP/IP stacks used in millions of #IoT#OT & IT devices. https://t.co/gHdtXLA5qj
#NAMEWRECK
As part of Project Memoria we're releasing a report together with @JSOF18 on several DNS vulnerabilities in popular TCP/IP stacks (FreeBSD, NetX, Nucleus NET, ...), including a breakdown of underlying anti-patterns (hint: check your message compression).
https://t.co/6rn5M9N8sl
The Qualys Research Team has discovered a critical vulnerability in #Sudo, which allows an unprivileged user to gain root privileges in its default configuration. #linux#unix#vulnerability https://t.co/JUAo8ULMu7
@eqhmcow@vijaycert@ICSCERT@certcc It was part of a different research project actually, not a specific target selection. The results of the original project will be published sometime soon. As separate a rule of thumb - clients tend to be less audited than servers, not always justified.
Supply chain issues affect Open Source Software too. Dnsmasq is extremely popular (and for a good reason!) and so the vulnerabilities affect dozens of vendors and many major Linux distributions.
Researchers have found set of flaws allowing for DNS cache-poisoning attacks (also known as DNS spoofing)
DNSpooq is a series of vulnerabilities found in the ubiquitous open-source software dnsmasq, demonstrating that DNS is still insecure
➡️https://t.co/0WXVPhKk9M
#DNSpooq
Some recommended workarounds for #dnspooq if you can't upgrade your device. Configuring your devices to directly query a trusted DNS server would also be helpful.
@serghei JSOF advises updating the Dnsmasq software to the latest version (2.83 or later) to fully mitigate DNSpooq attacks.
A list of (partial) workarounds is also available:
@maddiestone So, In context of found in-the-wild exploitation the term probably applies to any actor as you defined. It is also used otherwise for how attackers might use N-days and be no less sophisticated.
@maddiestone That is very impressive and interesting. There are also thousands of vulns reported yearly(many low-value ofc). Clearly those 24 are attributed to “sophisticated attackers”, at the same time, they can also do more than others with all the other vulns if/when not patched.
@maddiestone As in “a sophisticated attacker could use this vulnerability like that” is probably a more common phrase than “a sophisticated attacker can find &exploit a chain of vulnerabilities in this product”
@maddiestone Is the term “sophisticated attacker” widely used when discussing 0-days? It’s often used when discussing recently disclosed 1-days. If an attacker uses a true 0-day then nobody knows or can talk about that specific vuln (except for google TAG:)