First published: Thu Jan 25 2007(Updated: )
ISC BIND 9.0.x, 9.1.x, 9.2.0 up to 9.2.7, 9.3.0 up to 9.3.3, 9.4.0a1 up to 9.4.0a6, 9.4.0b1 up to 9.4.0b4, 9.4.0rc1, and 9.5.0a1 (Bind Forum only) allows remote attackers to cause a denial of service (exit) via a type * (ANY) DNS query response that contains multiple RRsets, which triggers an assertion error, aka the "DNSSEC Validation" vulnerability.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
BIND 9 | =9.2.0-rc7 | |
BIND 9 | =9.1.1-rc6 | |
BIND 9 | =9.3.1-rc1 | |
BIND 9 | =9.1.1 | |
BIND 9 | =9.2.3-rc2 | |
BIND 9 | =9.1.3 | |
BIND 9 | =9.1.1-rc1 | |
BIND 9 | =9.1.3-rc3 | |
BIND 9 | =9.4.0-b2 | |
BIND 9 | =9.2.0-b2 | |
BIND 9 | =9.3.2-rc1 | |
BIND 9 | =9.2.0-a3 | |
BIND 9 | =9.2.3-rc4 | |
BIND 9 | =9.2 | |
BIND 9 | =9.3.0-rc4 | |
BIND 9 | =9.2.4-rc8 | |
BIND 9 | =9.2.1-rc1 | |
BIND 9 | =9.3.0-rc2 | |
BIND 9 | =9.0.0-rc2 | |
BIND 9 | =9.4.0-a4 | |
BIND 9 | =9.3 | |
BIND 9 | =9.3.0-b2 | |
BIND 9 | =9.1.0-rc1 | |
BIND 9 | =9.0.0-rc1 | |
BIND 9 | =9.2.5 | |
BIND 9 | =9.3.2 | |
BIND 9 | =9.1.1-rc5 | |
BIND 9 | =9.2.3-rc3 | |
BIND 9 | =9.2.0-rc2 | |
BIND 9 | =9.2.5-b2 | |
BIND 9 | =9.2.2 | |
BIND 9 | =9.2.0-rc9 | |
BIND 9 | =9.4.0-a3 | |
BIND 9 | =9.5.0-a1 | |
BIND 9 | =9.0.0-rc3 | |
BIND 9 | =9.2.2-p2 | |
BIND 9 | =9.2.4-rc6 | |
BIND 9 | =9.3.0 | |
BIND 9 | =9.3.0-b3 | |
BIND 9 | =9.2.4-rc7 | |
BIND 9 | =9.1.3-rc2 | |
BIND 9 | =9.2.4 | |
BIND 9 | =9.2.5-rc1 | |
BIND 9 | =9.2.1 | |
BIND 9 | =9.1.2 | |
BIND 9 | =9.1.1-rc4 | |
BIND 9 | =9.4.0-a2 | |
BIND 9 | =9.3.1 | |
BIND 9 | =9.2.0-rc4 | |
BIND 9 | =9.1.1-rc3 | |
BIND 9 | =9.1 | |
BIND 9 | =9.2.1-rc2 | |
BIND 9 | =9.4.0-b3 | |
BIND 9 | =9.2.4-rc2 | |
BIND 9 | =9.2.2-p3 | |
BIND 9 | =9.1.3-rc1 | |
BIND 9 | =9.2.2-rc1 | |
BIND 9 | =9.2.0-rc3 | |
BIND 9 | =9.2.0-rc8 | |
BIND 9 | =9.0.1-rc2 | |
BIND 9 | =9.2.4-rc3 | |
BIND 9 | =9.0.0-rc6 | |
BIND 9 | =9.4.0-a1 | |
BIND 9 | =9.2.0-rc5 | |
BIND 9 | =9.3.0-rc1 | |
BIND 9 | =9.4.0-a5 | |
BIND 9 | =9.3.0-b4 | |
BIND 9 | =9.4.0-rc1 | |
BIND 9 | =9.3.0-rc3 | |
BIND 9 | =9.2.3 | |
BIND 9 | =9.2.0-rc6 | |
BIND 9 | =9.2.0-rc10 | |
BIND 9 | =9.2.0 | |
BIND 9 | =9.0.1 | |
BIND 9 | =9.2.0-a2 | |
BIND 9 | =9.1.1-rc2 | |
BIND 9 | =9.4.0-b1 | |
BIND 9 | =9.1.2-rc1 | |
BIND 9 | =9.2.4-rc4 | |
BIND 9 | =9.0.0-rc4 | |
BIND 9 | =9.0 | |
BIND 9 | =9.2.3-rc1 | |
BIND 9 | =9.2.0-b1 | |
BIND 9 | =9.2.4-rc5 | |
BIND 9 | =9.2.0-rc1 | |
BIND 9 | =9.0.0-rc5 | |
BIND 9 | =9.2.6-rc1 | |
BIND 9 | =9.0.1-rc1 | |
BIND 9 | =9.3.1-b2 | |
BIND 9 | =9.1.1-rc7 | |
BIND 9 | =9.2.6 | |
BIND 9 | =9.2.0-a1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-0494 has a severity rating of medium as it can lead to a denial of service.
To fix CVE-2007-0494, you should upgrade to a patched version of ISC BIND, specifically version 9.2.8 or later.
CVE-2007-0494 affects ISC BIND versions 9.0.x through 9.5.0a1, including various release candidates.
Yes, CVE-2007-0494 can be exploited remotely by sending malicious ANY DNS query responses.
The impact of CVE-2007-0494 is that it can cause the BIND service to exit unexpectedly, resulting in downtime.