Security readout for executives and security teams
Plain-English summary
This old FreeBSD issue affects certain port programs that use libkvm. They may leave access to kernel memory open, letting a local user read sensitive kernel memory. The concern is mainly legacy FreeBSD systems, not modern default environments based on the provided sources.
Executive priority
Treat as a legacy exposure review item. Prioritize if old FreeBSD hosts still support business functions or allow local user access. Otherwise, business urgency is low based on the limited source evidence.
Technical view
CVE-2002-1125 describes FreeBSD port programs using libkvm on FreeBSD 4.6.2-RELEASE and earlier. Named examples include asmon, ascpu, bubblemon, wmmon, and wmnet2. The flaw involves open file descriptors for /dev/mem and /dev/kmem, enabling local users to read kernel memory.
Likely exposure
Exposure is likely limited to FreeBSD 4.6.2-RELEASE and earlier systems running the named libkvm-using ports or similar affected port programs. Evidence for broader product impact is not provided.
Exploitation context
The source indicates local user access is required. There is no provided evidence of remote exploitation or active exploitation, and this CVE is not marked in KEV in the supplied data.
Researcher notes
Public data is sparse: no CVSS, CWE, references, patch details, or affected CPEs are included. The clearest technical fact is local kernel memory disclosure through inherited open descriptors in libkvm-using ports.
Mitigation direction
- Inventory FreeBSD systems at 4.6.2-RELEASE or earlier.
- Identify installed ports using libkvm, including the named examples.
- Remove or disable affected port programs where not required.
- Restrict local shell access on legacy FreeBSD hosts.
- Check FreeBSD and port maintainer guidance for historical fixes.
Validation and detection
- Confirm FreeBSD version on potentially legacy hosts.
- Check whether asmon, ascpu, bubblemon, wmmon, or wmnet2 are installed.
- Review whether similar ports use libkvm and access /dev/mem or /dev/kmem.
- Verify untrusted users cannot log in locally.
- Document compensating controls for any retained legacy systems.
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-2002-1125 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.