Security readout for executives and security teams
Plain-English summary
This legacy CVE describes a ypserv flaw where a local user could change other users' descriptive account fields and login shells. The business impact depends on whether NIS/ypserv still exists in the environment. The source bundle does not identify affected vendors, versions, CVSS, or a named patch.
Executive priority
Treat this as a legacy exposure question, not a confirmed emergency. If NIS/ypserv is absent, business risk is likely negligible. If present on multi-user systems, prioritize vendor verification and containment because account shell changes can affect access control and operational integrity.
Technical view
CVE-1999-0901 concerns ypserv and improper control over account metadata changes. A local user may modify other users' GECOS fields and login shells. The provided CVE data lacks affected product details, CWE mapping, CVSS scoring, and remediation specifics, limiting precise exposure analysis.
Likely exposure
Most likely limited to legacy Unix/Linux environments still using NIS/ypserv with local user access. The bundle lists affected vendor, product, versions, and CPEs as unavailable, so asset confirmation is required.
Exploitation context
The provided data supports local-user misuse potential only. There is no KEV listing and no cited source in the bundle indicating active exploitation, remote exploitation, public exploit availability, or weaponized campaigns.
Researcher notes
Evidence is sparse: the CVE description identifies behavior, but not vulnerable versions, products, root cause, patch level, or exploitation prerequisites beyond local user access. Do not infer remote reachability or specific distributions without vendor advisories or host evidence.
Mitigation direction
- Inventory systems for current or historical NIS/ypserv usage.
- Check operating system or ypserv vendor guidance for fixed packages or configuration advice.
- Prioritize systems where untrusted users have local accounts.
- Review whether NIS can be retired or isolated in legacy segments.
Validation and detection
- Confirm whether any production hosts run ypserv or depend on NIS.
- Review account records for unexpected GECOS or login shell changes.
- Check change records around shared account-management infrastructure.
- Map any identified ypserv instances to vendor-supported versions.
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-0901 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-0901CVE 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.