Security readout for executives and security teams
Plain-English summary
CVE-1999-0371 describes an old Lynx issue where a local user could abuse temporary-file symlinks to overwrite sensitive files. The bundle does not identify affected versions, a CVSS score, or a named patch. Treat exposure as possible only where Lynx is installed on multi-user systems.
Executive priority
Moderate operational priority for legacy or multi-user Unix-like environments. Business urgency is lower without evidence of active exploitation, but sensitive-file overwrite risk warrants inventory and vendor-advisory review.
Technical view
The vulnerability is a local temporary-file handling flaw involving /tmp symlinks in Lynx, allowing file overwrite under vulnerable conditions. Public metadata in the bundle is sparse: no CPEs, versions, CVSS, CWE, or remediation details are provided.
Likely exposure
Likely exposure is limited to systems with Lynx installed and accessible to local users. Exact vulnerable versions and platforms are not provided in the supplied sources.
Exploitation context
The source bundle supports local exploitation context only. It does not indicate remote exploitation, public exploit availability, or active exploitation; KEV status is false.
Researcher notes
Evidence is incomplete. The record names Lynx and /tmp symlink file overwrite, but omits affected versions, prerequisites beyond local access, patch details, and severity scoring. Avoid broad product or version claims without vendor advisories.
Mitigation direction
- Inventory systems where Lynx is installed or available to local users.
- Check operating-system and Lynx vendor guidance for affected versions and fixes.
- Upgrade, remove, or disable Lynx where vendor guidance indicates exposure.
- Prioritize multi-user servers and systems with sensitive local files.
Validation and detection
- Confirm Lynx package presence and version on managed systems.
- Compare installed packages against vendor or distribution advisories.
- Review whether untrusted local users can access affected hosts.
- Check file integrity monitoring for unexpected sensitive-file changes.
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-0371 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-0371CVE 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.