ZeroHour

Search: “cache poisoning”

156 stories

Six new dnsmasq vulnerabilities open the door to DNS cache poisoning, local root

Six dnsmasq flaws enable DNS cache poisoning, DoS, memory leaks, and local root code execution; fixes ship in version 2.92rel2.

Researchers disclosed six dnsmasq vulnerabilities spanning memory safety and input validation, including heap buffer overflows in extract_name() and extract_addresses(), DNSSEC infinite-loop and out-of-bounds read flaws, and a DHCPv6 out-of-bounds write allowing local root code execution. Exploitation paths include DNS cache poisoning, bypassing security controls, remote denial of service, and local privilege escalation. Maintainers released version 2.92rel2 with fixes, and a stable 2.93 release is expected within weeks.

USN-8742-1: Netty vulnerability

Ubuntu issues USN-8742-1 fixing a Netty DNS cache poisoning flaw caused by improper NS record bailiwick validation.

Ubuntu Security Notice USN-8742-1 addresses a vulnerability in the Netty framework in which NS records are incorrectly validated for bailiwick. An attacker could potentially exploit this to facilitate DNS cache poisoning attacks. Updated packages are available for supported Ubuntu releases.

Ubuntu Security Noticesupdated · 4d agofirst · 6d agoAdvisory 13 sources

Automatically Detecting DNS Hijacking in Passive DNS

Unit 42's machine learning pipeline detected 6,729 DNS hijacking events between March and September 2024, hitting political parties, ISPs, and universities.

Unit 42 processes roughly 167 million new DNS records daily and applies a machine learning model using 74 features over 169 TB of passive DNS and geolocation data to flag hijacked domains. From March to September 2024 the pipeline screened over 29 billion records and classified 6,729 as DNS hijacking, averaging 38 detections per day; a new model detects hijacks in customer traffic within about 10 minutes. Notable cases include a Hungarian political party's hijacked domain, defacement of a large utility company and ISP, and university and research center domains repurposed for illicit gambling. DNS hijacking typically relies on stolen registrar or DNS provider credentials or cache poisoning, enabling MitM attacks, phishing, drive-by downloads, and scams.

Palo Alto Unit 42 · 29d agoResearch in the wild