Security readout for executives and security teams
Plain-English summary
CVE-2012-1191 affects dnscache in djbdns 1.05. A resolver can keep resolving domain names after they should have been revoked, because cached DNS server-name and TTL data can be overwritten during certain DNS responses. This is a DNS trust and availability concern, not evidence of host takeover.
Executive priority
Treat this as a targeted DNS infrastructure risk. Prioritize if djbdns 1.05 dnscache supports production name resolution, especially for security-sensitive environments. If it is not deployed, no action is indicated beyond documentation.
Technical view
The issue is in dnscache’s resolver cache handling. While processing an A record response, it can overwrite cached server names and TTL values in NS records, enabling a “ghost domain names” condition where revoked domains remain resolvable through the affected cache.
Likely exposure
Exposure is limited to organizations running Daniel J. Bernstein djbdns 1.05 dnscache as a caching or recursive DNS resolver. The source bundle does not identify other affected products, versions, or distributions.
Exploitation context
The CVE states remote attackers can trigger continued resolvability of revoked domain names. CISA KEV status is false in the bundle, and no provided source confirms active exploitation in the wild.
Researcher notes
Evidence is narrow: the CVE description names djbdns 1.05 dnscache and a ghost-domain behavior. The bundle provides no CVSS, CWE, patch identifier, proof of active exploitation, or named downstream packages. Avoid broad product conclusions without further vendor evidence.
Mitigation direction
- Inventory any dnscache or djbdns 1.05 resolver deployments.
- Check maintainer, distribution, or vendor guidance for supported fixes or replacement advice.
- Consider retiring unsupported djbdns 1.05 resolver use after operational review.
- Restrict resolver access to trusted clients where business requirements allow.
- Monitor DNS behavior for unexpected resolution of revoked or changed domains.
Validation and detection
- Confirm whether djbdns 1.05 dnscache is deployed in DNS resolver paths.
- Review resolver configuration to identify who can query the cache.
- Check whether revoked or redelegated domains continue resolving unexpectedly.
- Correlate DNS logs with domain revocation or delegation-change events.
- Document affected resolver instances and business services depending on them.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2012-1191 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.isc.org/files/imce/ghostdomain_camera.pdfCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.