CVE-2025-40780
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-22

Last updated on: 2025-11-04

Assigner: Internet Systems Consortium (ISC)

Description
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. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.16.8-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-22
Last Modified
2025-11-04
Generated
2026-05-07
AI Q&A
2025-10-22
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 100 associated CPEs
Vendor Product Version / Range
isc bind 9.18.5
isc bind 9.18.25
isc bind 9.16.21
isc bind 9.18.23
isc bind 9.16.19
isc bind 9.18.35
isc bind 9.18.10
isc bind 9.16.38
isc bind 9.18.19
isc bind 9.16.18
isc bind 9.18.13
isc bind 9.16.36
isc bind 9.16.2
isc bind 9.18.9
isc bind 9.16.16
isc bind 9.18.29
isc bind 9.20.1
isc bind 9.18.7
isc bind 9.16.48
isc bind 9.16.31
isc bind 9.18.1
isc bind 9.16.37
isc bind 9.16.32
isc bind 9.16.23
isc bind 9.18.27
isc bind 9.18.6
isc bind 9.20.2
isc bind 9.16.28
isc bind 9.16.1
isc bind 9.16.41
isc bind 9.16.15
isc bind 9.16.9
isc bind 9.16.12
isc bind 9.18.26
isc bind 9.18.16
isc bind 9.18.22
isc bind 9.16.7
isc bind 9.16.33
isc bind 9.18.14
isc bind 9.18.18
isc bind 9.16.11
isc bind 9.16.40
isc bind 9.16.27
isc bind 9.16.4
isc bind 9.20.5
isc bind 9.18.2
isc bind 9.18.3
isc bind 9.16.49
isc bind 9.16.10
isc bind 9.18.11
isc bind 9.18.33
isc bind 9.16.26
isc bind 9.16.3
isc bind 9.20.6
isc bind 9.20.3
isc bind 9.18.36
isc bind 9.18.30
isc bind 9.16.5
isc bind 9.20.0
isc bind 9.16.14
isc bind 9.16.17
isc bind 9.16.34
isc bind 9.16.43
isc bind 9.20.7
isc bind 9.16.30
isc bind 9.18.12
isc bind 9.16.13
isc bind 9.16.8
isc bind 9.18.34
isc bind 9.18.28
isc bind 9.18.31
isc bind 9.18.21
isc bind 9.18.39
isc bind 9.16.8-s1
isc bind 9.18.17
isc bind 9.16.46
isc bind 9.20.4
isc bind 9.18.37
isc bind 9.16.50
isc bind 9.16.44
isc bind 9.16.42
isc bind 9.18.24
isc bind 9.18.32
isc bind 9.16.39
isc bind 9.18.4
isc bind 9.16.25
isc bind 9.16.0
isc bind 9.16.6
isc bind 9.18.20
isc bind 9.16.24
isc bind 9.18.38
isc bind 9.16.35
isc bind 9.18.0
isc bind 9.16.20
isc bind 9.16.45
isc bind 9.18.8
isc bind 9.18.15
isc bind 9.16.29
isc bind 9.16.22
isc bind 9.16.47
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-341 A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in BIND 9 arises from a weakness in the Pseudo Random Number Generator (PRNG) used by BIND, which allows an attacker to predict the source port and query ID values that BIND will use in DNS queries. This predictability enables an attacker to perform DNS cache poisoning by injecting malicious responses that BIND will accept and cache, compromising the integrity of DNS resolution. [1]


How can this vulnerability impact me? :

The vulnerability can impact you by allowing an attacker to perform DNS cache poisoning attacks against DNS resolvers running vulnerable BIND versions. This means an attacker could inject malicious DNS responses, causing your system to resolve domain names incorrectly, potentially redirecting you to malicious sites or disrupting normal network operations. The integrity of DNS resolution is compromised, but confidentiality and availability are not directly affected. [1]


What immediate steps should I take to mitigate this vulnerability?

The immediate step to mitigate this vulnerability is to upgrade BIND to the patched versions recommended by ISC. These versions are 9.18.41, 9.20.15, 9.21.14, and for Supported Preview Editions, 9.18.41-S1 and 9.20.15-S1. No workarounds are currently known, so upgrading is the advised mitigation. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart