Security readout for executives and security teams
Plain-English summary
CVE-1999-0851 is an old denial-of-service issue in BIND named involving NAPTR DNS records. The public CVE data does not identify affected versions, severity, fixes, or confirmed exploitation. Treat it as a legacy DNS risk requiring inventory verification rather than an emergency without further vendor evidence.
Executive priority
Medium-low until affected legacy BIND systems are found. DNS outages can be business-impacting, but the public record lacks severity, affected versions, and exploitation evidence. Prioritize asset discovery and unsupported software remediation.
Technical view
The CVE record describes a denial of service in BIND named via NAPTR. No CVSS, CWE, affected-version, patch, or advisory details are present in the provided public sources. NAPTR is a DNS record type, so exposure would relate to BIND named servers processing such records.
Likely exposure
Potential exposure is limited to environments running BIND named, but the provided sources do not state affected versions or configurations. Internet-facing authoritative or recursive DNS servers would have higher business relevance if they rely on BIND named.
Exploitation context
The provided data does not show CISA KEV listing, active exploitation, public exploit status, or technical prerequisites. The issue is described only as denial of service via NAPTR, so impact appears availability-focused based on the CVE description.
Researcher notes
Evidence is sparse: the CVE description is a single-line DoS statement, with no version range or fix metadata. Avoid assuming modern BIND exposure without corroborating vendor advisories or local version evidence.
Mitigation direction
- Inventory BIND named deployments and versions.
- Check current ISC/BIND vendor guidance for historical NAPTR denial-of-service fixes.
- Prioritize internet-facing DNS infrastructure for review.
- Ensure DNS service monitoring and restart procedures are documented.
- Plan upgrades for unsupported or legacy BIND installations.
Validation and detection
- Confirm whether BIND named is used in production DNS paths.
- Identify BIND versions on authoritative and recursive servers.
- Review vendor advisories or changelogs for CVE-1999-0851 references.
- Check DNS monitoring for unexplained named crashes or restarts.
- Document whether affected legacy versions remain in service.
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-1999-0851 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
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.