CVE-1999-0024

mediumpriority · track · 22EPSS 0.050 · 92 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
4.98% (92nd) EPSS
CVSS 5 · medium
Is it mine?
24 products
Check your exposure
Who says so?
2 sources
enisa_euvd · nvd

EPSS · scored 2026-10-27

DNS cache poisoning via BIND, by predictable query IDs.

01

cvss

Technical severity, 0–10. One row per scoring source.

5.0
010

base score 0–10 · higher = more severe · hover a vector to decode

v2.05mediumAV:N/AC:L/Au:N/C:N/I:P/A:Nprimary · NVD / NIST USexploitability 10 · impact 2.9
v2.04.3mediumAV:N/AC:L/Au:N/C:N/I:P/A:N/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-284USLLM-inferredCWE-310USLLM-inferred
04

affected products (24)

Products and version ranges known to be affected.

showing 20 of 24
05

also known as (2)

Other names and identifiers for this entity.

06

sources

Which sources assert this record, and when.

published 1997-08-13modified 2026-10-09
07

references (2)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan