Security readout for executives and security teams
Plain-English summary
This older CVE describes a local-user flaw in Red Hat Linux's screen program. Because screen did not use Unix98 pseudo-terminals, a local user could write to another user's terminal. The sources do not provide CVSS, affected versions, patch details, or evidence of active exploitation.
Executive priority
Treat as a legacy hygiene issue unless affected multi-user Red Hat Linux systems are still in operation. Prioritize inventory and retirement or upgrade of unsupported hosts.
Technical view
The described weakness is terminal isolation failure in Red Hat Linux screen: non-use of Unix98 ptys allowed local users to write to other terminals. Available records are sparse and identify no CWE, exact package versions, fixed releases, exploit status, or vendor remediation text.
Likely exposure
Exposure is most plausible on legacy Red Hat Linux systems with the affected screen program installed and multiple local interactive users. The provided sources do not identify exact versions or supported products.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The described attack requires local user access and affects terminal confidentiality/integrity rather than remote entry.
Researcher notes
Evidence is limited to short CVE/X-Force descriptions. Do not assume broader GNU screen impact, affected versions, or fixed builds without additional vendor advisories.
Mitigation direction
- Check Red Hat or distribution guidance for historical screen fixes.
- Inventory legacy Red Hat Linux hosts running screen.
- Restrict interactive shell access to trusted users on exposed legacy hosts.
- Retire, isolate, or upgrade unsupported systems where remediation is unclear.
Validation and detection
- Confirm whether any Red Hat Linux hosts still run screen.
- Identify screen package versions and compare against vendor guidance.
- Review systems with multiple local shell users for heightened exposure.
- Check access controls for interactive terminal sessions on legacy hosts.
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-0894 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-0894CVE 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.