Security readout for executives and security teams
Plain-English summary
This CVE describes systems running rwho/rwhod, a status-sharing service that exposes machine status and user information. The business risk is information leakage, not confirmed code execution. The supplied sources do not identify affected products, versions, CVSS severity, or a vendor patch.
Executive priority
Handle as a legacy service exposure cleanup. Prioritize externally reachable or sensitive systems first, but urgency cannot be rated precisely from the supplied CVE data.
Technical view
CVE-1999-0628 is an information exposure finding for the rwho/rwhod service being active. The record provides no CVSS, CWE, affected CPEs, exploit details, or product-specific remediation. Treat it as a configuration exposure requiring asset validation and vendor guidance.
Likely exposure
Exposure is limited to systems where rwho/rwhod is installed, enabled, or reachable. The supplied sources do not name specific operating systems, vendors, versions, or internet exposure patterns.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The risk is that exposed status and user data can support reconnaissance and operational mapping.
Researcher notes
Evidence is sparse: description only, severity unknown, no CVSS, no CWE, and no affected product list. Avoid broad claims beyond rwho/rwhod information exposure unless additional vendor evidence is obtained.
Mitigation direction
- Inventory hosts running or exposing rwho/rwhod.
- Check operating system or vendor guidance for supported remediation.
- Disable rwho/rwhod where it is not explicitly required.
- Restrict service reachability to trusted management networks if retained.
- Document business justification for any remaining enabled instances.
Validation and detection
- Confirm whether rwho/rwhod is enabled on in-scope hosts.
- Review network access paths to any reachable service instances.
- Verify exposed hosts no longer share user or machine status unnecessarily.
- Record exceptions with owner, purpose, and review date.
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-0628 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-0628CVE 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.