cve.bz

CVE-2002-2212

no score yetEPSS 2.5%Fix available

No CVSS score yet. EPSS 2.5% estimated probability of exploitation activity in the next 30 days.

On this page
The DNS resolver in unspecified versions of Fujitsu UXP/V, when resolving recursive DNS queries for arbitrary hosts, allows remote attackers to conduct DNS cache poisoning via a birthday attack that uses a large number of open queries for the same resource record (RR) combined with spoofed responses, which increases the possibility of successfully spoofing a response in a way that is more efficient than brute force methods.
EPSS
2.5% (unchanged from 2.5% a week ago; 2.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 85th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2002-2212 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2002-2212?via=ask-ai-copy and https://cve.bz/cve/CVE-2002-2212?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2002-2212 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
isc:bind4.9
isc:bind4.9.2
isc:bind4.9.3
isc:bind4.9.4
isc:bind4.9.5
isc:bind4.9.5:p1
isc:bind4.9.6
isc:bind4.9.7
isc:bind4.9.8
isc:bind4.9.9
isc:bind4.9.10
isc:bind8.2
isc:bind8.2.1
isc:bind8.2.2
isc:bind8.2.2:p1
isc:bind8.2.2:p2
isc:bind8.2.2:p3
isc:bind8.2.2:p4
isc:bind8.2.2:p5
isc:bind8.2.2:p6
isc:bind8.2.2:p7
isc:bind8.2.3
isc:bind8.2.4
isc:bind8.2.5
isc:bind8.2.6
isc:bind8.2.7
isc:bind8.3.0
isc:bind8.3.1
isc:bind8.3.2
isc:bind8.3.3
isc:bind8.3.4

References

Check your stackJSON