“In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use,” BIND developers wrote in Wednesday’s disclosure. “BIND can be tricked into caching attacker responses, if the spoofing is successful.”
CVE-2025-40778 also raises the possibility of reviving cache poisoning attacks.
“Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache,” the developers explained. “Forged records can be injected into cache during a query, which can potentially affect resolution of future queries.”
Even in such cases, the resulting fallout would be significantly more limited than the scenario envisioned by Kaminsky. One reason for that is that authoritative servers themselves aren’t vulnerable. Further, as noted here and here by Red Hat, various other cache poisoning countermeasures remain intact. They include DNSSEC, a protection that requires DNS records to be digitally signed. Additional measures come in the form of rate limiting and server firewalling, which are considered best practices.
“Because exploitation is non-trivial, requires network-level spoofing and precise timing, and only affects cache integrity without server compromise, the vulnerability is considered Important rather than Critical,” Red Hat wrote in its disclosure of CVE-2025-40780.
The vulnerabilities nonetheless have the potential to cause harm in some organizations. Patches for all three should be installed as soon as practicable.
Source link
#Cache #poisoning #vulnerabilities #DNS #resolving #apps
