LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0799: Buffer overflow in bootpd 2.4.3 and earlier via a long boot file location.

Buffer overflow in bootpd 2.4.3 and earlier via a long boot file location.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-1999-0799 is an old buffer overflow in bootpd 2.4.3 and earlier involving an overly long boot file location. The public bundle does not provide CVSS, confirmed impact, vendor fix details, or exploitation evidence. Treat exposure as a legacy infrastructure hygiene issue unless the service is still reachable.

Executive priority

Prioritize based on confirmed exposure. If bootpd is absent, no action beyond documentation is needed. If present and reachable, retire or isolate it because the software is obsolete and the source bundle gives no modern patch assurance.

Technical view

The CVE description states bootpd 2.4.3 and earlier can overflow a buffer when processing a long boot file location. The bundle does not identify vendor packaging, vulnerable platforms, privilege context, crash versus code execution impact, or patches. KEV status is false.

Likely exposure

Likely limited to legacy systems still running bootpd 2.4.3 or earlier, especially environments using BOOTP or network boot services. Exposure is higher if the service is reachable from untrusted networks. The source bundle lists affected vendor and product as n/a, so asset confirmation is required.

Exploitation context

No active exploitation is stated in the supplied sources, and the CVE is not marked KEV. The vulnerability is theoretically concerning because buffer overflows in network daemons can affect availability or control flow, but the provided evidence does not confirm practical exploitability.

Researcher notes

Evidence is sparse: the CVE Program description and referenced X-Force entry identify the issue, version boundary, and trigger class only. No CVSS, CWE, platform list, exploit status, or remediation text is supplied. Avoid expanding scope beyond bootpd 2.4.3 and earlier.

Mitigation direction

  • Inventory systems for bootpd 2.4.3 or earlier.
  • Disable bootpd where BOOTP service is not required.
  • Restrict BOOTP access to trusted network segments only.
  • Check operating system or vendor guidance for replacement packages or fixes.
  • Monitor for unexpected BOOTP traffic to legacy hosts.

Validation and detection

  • Confirm whether any hosts run bootpd and record exact versions.
  • Review network exposure for BOOTP service reachability.
  • Verify only trusted clients can access required BOOTP services.
  • Check vulnerability scanner results for legacy bootpd findings.
  • Document compensating controls if retirement is not immediate.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-1999-0799 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.