Security readout for executives and security teams
Plain-English summary
A legacy Unix file-transfer service known as BNU UUCP could be crashed or hijacked when someone sent it an unusually long hostname. Attackers who reached the service could potentially overwrite memory and take control of the affected system. The issue is decades old and mostly relevant today only where obsolete UUCP daemons still run on internet-reachable or trusted network segments.
Executive priority
Low priority for most modern environments. Treat as a hygiene item during legacy system reviews; escalate only if an inventory scan confirms an internet-reachable or unpatched uucpd instance.
Technical view
Per the CVE record, BNU UUCP's uucpd daemon contains a buffer overflow triggered by overly long hostname input. The bundled sources do not enumerate affected vendors, versions, CVSS, CWE, or patch data. Historically, uucpd listened on TCP/540 and processed hostname strings without bounds checking, enabling stack corruption. No KEV listing and no exploitation telemetry is cited in the provided bundle.
Likely exposure
Exposure is expected to be very narrow in 2026. UUCP has been deprecated for decades and is rarely deployed. Risk concentrates on legacy Unix systems, industrial or academic archives, or unmaintained appliances that still expose uucpd on a network interface.
Exploitation context
The provided sources do not indicate active exploitation, and CISA KEV does not list this CVE. The bundle marks severity as unknown and references only a single X-Force entry without exploit availability or in-the-wild reports.
Researcher notes
Bundle lacks CWE, CVSS, CPE, and patch references, so scope must be inferred from historical knowledge of BNU UUCP. No KEV entry and no cited exploit. Recommend confirming presence via targeted service discovery rather than trusting asset inventories, since legacy Unix hosts are often undocumented.
Mitigation direction
- Disable uucpd on any host where UUCP is not a documented business requirement.
- Block inbound TCP/540 at the perimeter and internal firewalls.
- Retire or isolate legacy Unix systems still running BNU UUCP.
- Consult the OS or appliance vendor for any historical patches before re-enabling the service.
Validation and detection
- Inventory hosts for a listening uucpd process or TCP/540 listener.
- Confirm whether UUCP is required by any current business or integration process.
- Review firewall and IDS logs for connection attempts to UUCP ports.
- Check vendor advisories for the specific Unix distribution regarding uucpd patches.
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-0303 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://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0303CVE 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.