CVE-2009-0233 json
The DNS Resolver Cache Service (aka DNSCache) in Windows DNS Server in Microsoft Windows 2000 SP4, Server 2003 SP1 and SP2, and Server 2008…
published 2009-03-11 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0241
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 27.1%
- EPSS 27.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The DNS Resolver Cache Service (aka DNSCache) in Windows DNS Server in Microsoft Windows 2000 SP4, Server 2003 SP1 and SP2, and Server 2008, when dynamic updates are enabled, does not reuse cached DNS responses in all applicable situations, which makes it easier for remote attackers to predict transaction IDs and poison caches by simultaneously sending crafted DNS queries and responses, aka "DNS Server Query Validation Vulnerability."
Exploit prediction
27.07% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-008
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6228
vdb-entry, signature
-
us-cert.gov
/cas/techalerts/TA09-069A.html
third-party-advisory, us-government-resource
-
vupen.com
/english/advisories/2009/0661
vdb-entry
-
secunia.com
/advisories/34217
third-party-advisory
-
securityfocus.com
/bid/33982
vdb-entry
- support.avaya.com /elmodocs2/security/ASA-2009-083.htm
-
securitytracker.com
/id?1021831
vdb-entry
- blogs.technet.com /srd/archive/2009/03/13/ms09-008-dns-and-wins-server-security-update-in-more-detail.aspx
-
osvdb.org
/52517
vdb-entry
Sources
- CVE List CVE-2009-0233
- NVD CVE-2009-0233
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.