Security readout for executives and security teams
Plain-English summary
This is an old CVE describing a buffer overflow in the Dosemu Slang library on Linux. The public record does not state affected versions, impact, severity, or a vendor fix. Treat it as a legacy software risk requiring inventory confirmation rather than an emergency without more evidence.
Executive priority
Low-to-review priority unless legacy Dosemu systems are in use. The main business action is asset discovery and retirement or update planning for obsolete Linux components.
Technical view
CVE-1999-0390 is recorded as a buffer overflow in the Dosemu Slang library in Linux. The CVE data lacks CVSS, CWE, affected version ranges, references, and remediation details. No CISA KEV entry is indicated in the provided sources.
Likely exposure
Likely limited to systems running legacy Dosemu-related Slang library components on Linux. Exposure cannot be confirmed from the CVE record because affected packages, distributions, and versions are not specified.
Exploitation context
The provided sources do not report active exploitation, public exploit availability, required access, or practical impact. Buffer overflows can be serious, but this record is too sparse to assess exploitability confidently.
Researcher notes
The CVE record is minimal and contains no references or version data. Avoid assuming impact, exploitability, or remediation beyond confirming Dosemu Slang presence and consulting vendor or distribution archives.
Mitigation direction
- Inventory Linux systems for Dosemu and related Slang library packages.
- Check operating system and Dosemu vendor advisories for historical fixes or package updates.
- Remove Dosemu components where no business need exists.
- Prefer supported distribution packages over unmaintained legacy builds.
- Apply available vendor or distribution updates if identified.
Validation and detection
- Confirm whether Dosemu-related Slang components are installed on Linux assets.
- Record package names, versions, source repositories, and installation paths.
- Compare installed versions against vendor or distribution security advisories.
- Verify unsupported legacy systems are documented and risk accepted or retired.
- Monitor CVE and distribution records for additional historical context.
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-0390 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
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.