CVE-1999-0024: DNS cache poisoning via BIND, by predictable query IDs.

17

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 5% (30-day exploitation probability)+14
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

4.98%

ahead of 92% of scored CVEs · Oct 14, 2026

Affects

Bsdi

Bsd Os and 11 more

CVSS base

5.0

Medium · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Bsdi Bsd Os, Ibm Aix, Isc Bind…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
EPSS ahead of 92% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Bsdi	Bsd Os	version 2.1version 3.0	Vulnerable	NIST National Vulnerability Database
Ibm	Aix	version 4.1version 4.2	Vulnerable	NIST National Vulnerability Database
Isc	Bind	version 8.1version 4.9.5	Vulnerable	NIST National Vulnerability Database
Nec	Asl Ux 4800	version 64	Vulnerable	NIST National Vulnerability Database
Nec	Ews-ux V	version 4.2version 4.2mp	Vulnerable	NIST National Vulnerability Database
Nec	Up-ux V	version 4.2mp	Vulnerable	NIST National Vulnerability Database
Sco	Open Desktop	version 3.0	Vulnerable	NIST National Vulnerability Database
Sco	Openserver	version 5.0	Vulnerable	NIST National Vulnerability Database
Sco	Unix	version 3.2v4	Vulnerable	NIST National Vulnerability Database
Sco	Unixware	version 2.1	Vulnerable	NIST National Vulnerability Database
Sun	Solaris	version 2.4version 2.5version 2.5.1version 2.6	Vulnerable	NIST National Vulnerability Database
Sun	Sunos	versions not specified by the sourceversion 5.3version 5.4version 5.5version 5.5.1	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.0	CVSS 2.0	Medium	10.0	2.9	nvd@nist.gov via NIST National Vulnerability Database

AV:N/AC:L/Au:N/C:N/I:P/A:N (score shown at the top: nvd@nist.gov)

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 4.98%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 5.0
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
1997
CVE published
Aug 13, 1997 · mitre

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0024
x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

Bsdi
every CVE for this vendor

Related CVEs (same products)

High CVE-2026-16821 Use of Externally-Controlled Format String in Ibm Aix Aug 28, 2026
High CVE-2026-19448 Use of Uninitialized Resource in Ibm Vios Aug 20, 2026
High CVE-2026-19442 Untrusted Pointer Dereference in Ibm Vios Aug 20, 2026
High CVE-2026-19446 Uncontrolled Resource Consumption in Ibm Vios Aug 20, 2026
High CVE-2026-19449 Improper Privilege Management in Ibm Vios Aug 20, 2026
High CVE-2026-19783 Out-of-bounds Write in Ibm Vios Aug 20, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-1999-0024 is "DNS cache poisoning via BIND, by predictable query IDs.", rated Medium. It affects Bsd Os (Bsdi); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.0 describes technical severity. EPSS 4.98% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.