LiveActive security incident?Get immediate response
CVE Record

CVE-2009-4022: Unspecified vulnerability in ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P4, 9.5 before 9.5.2-P1, 9.6 be...

Unspecified vulnerability in ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P4, 9.5 before 9.5.2-P1, 9.6 before 9.6.1-P2, and 9.7 beta before 9.7.0b3, with DNSSEC validation enabled and checking disabled (CD), allows remote attackers to conduct DNS cache poisoning attacks by receiving a recursive client query and sending a response that contains an Additional section with crafted data, which is not properly handled when the response is processed "at the same time as requesting DNSSEC records (DO)," aka Bug 20438.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2009-4022 affects older ISC BIND recursive DNS servers in certain DNSSEC configurations. An attacker could poison the DNS cache, causing users to be directed to incorrect destinations. This can undermine trust in name resolution for business services. The issue is old, but any remaining exposed legacy BIND resolver should be treated urgently. Exposure is likely limited to legacy ISC BIND 9 recursive resolvers running affected versions with DNSSEC validation enabled and CD-related conditions present. Authoritative-only servers are not clearly implicated by the provided description. Prioritize remediation where legacy BIND resolvers serve employees, customers, or production systems. DNS cache poisoning can redirect traffic and damage trust, even without server takeover. This is mainly a legacy-exposure risk. Mitigation focus: Upgrade affected BIND installations to the fixed versions identified in the CVE or later supported releases.; Apply distribution-specific BIND security updates from vendors such as ISC, Ubuntu, Red Hat, IBM, or VMware where applicable.; Review vendor advisories for any configuration-specific mitigation if immediate patching is not possible..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-4022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
13Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.