CVE-2025-40780: Cache poisoning due to weak PRNG
Cache poisoning due to weak PRNG
Other sources
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.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 21.0.0.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.5.1.417.1.3.1 - Upgrade
Upgrade
ISC BIND 9to a version that resolves this vulnerability.Fixed in 9.18.41 - Upgrade
Upgrade
ISC BIND 9to a version that resolves this vulnerability.Fixed in 9.20.15 - Upgrade
Upgrade
ISC BIND 9to a version that resolves this vulnerability.Fixed in 9.21.14 - Upgrade
Upgrade
ISC BIND 9to a version that resolves this vulnerability.Fixed in 9.18.41-S1 - Upgrade
Upgrade
ISC BIND 9to a version that resolves this vulnerability.Fixed in 9.20.15-S1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-40780?
CVE-2025-40780 has been assigned a medium severity rating due to its potential for predictable source port and query ID exploitation.
How do I fix CVE-2025-40780?
To fix CVE-2025-40780, upgrade to BIND 9 versions 9.16.51 or later, 9.18.40 or later, or 9.20.14 or later.
Which versions of BIND are affected by CVE-2025-40780?
BIND versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, and 9.21.0 through 9.21.12 are affected.
What types of attacks could exploit CVE-2025-40780?
CVE-2025-40780 could be exploited in DNS cache poisoning attacks where an attacker predicts port and query ID values.
Is CVE-2025-40780 fixed in the latest BIND versions?
Yes, the latest BIND versions post the specified vulnerable ranges include fixes for CVE-2025-40780.