Security readout for executives and security teams
Plain-English summary
This is a legacy FreeBSD local privilege-escalation issue. On FreeBSD 4.6 and earlier, certain file descriptor handling involving procfs or linprocfs could let a local user influence privileged programs and gain elevated privileges.
Executive priority
Prioritize if any legacy FreeBSD 4.6-or-earlier systems remain in production or support multi-user access. Otherwise, business urgency is low, but the issue should inform legacy system decommissioning and hardening plans.
Technical view
The FreeBSD kernel may close file descriptors 0, 1, and 2 after assigning them to /dev/null when those descriptors reference procfs or linprocfs. Reuse of those descriptors in setuid or setgid programs could allow modification of sensitive data and privilege escalation.
Likely exposure
Exposure is mainly legacy FreeBSD systems running kernel 4.6 or earlier, especially where untrusted local users can log in or run code. Modern environments are unlikely to be affected unless old FreeBSD installations remain in production.
Exploitation context
The provided sources do not show active exploitation, public exploit status, CVSS scoring, or named affected package versions beyond FreeBSD 4.6 and earlier. Exploitation requires local access and interaction with privileged setuid or setgid program behavior.
Researcher notes
Source data is sparse. The CVE description provides the vulnerability mechanism, but no CVSS, CWE, patch reference, advisory link, or exploit evidence is included in the provided bundle.
Mitigation direction
- Identify and retire or upgrade FreeBSD 4.6 and earlier systems.
- Check FreeBSD vendor advisories for the appropriate historical fix or upgrade path.
- Restrict local shell or code execution access on affected legacy hosts.
- Review necessity of procfs and linprocfs on legacy systems.
Validation and detection
- Inventory hosts running FreeBSD kernel 4.6 or earlier.
- Confirm whether procfs or linprocfs is enabled on those hosts.
- Review local user access to affected legacy systems.
- Review setuid and setgid program exposure on affected 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-0820 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.