Security readout for executives and security teams
Plain-English summary
This CVE describes a legacy UMN gopher/gopher+ flaw that could let an intruder read files accessible to the gopher daemon. Business impact depends on whether any old Gopher service remains reachable and what that daemon account can access.
Executive priority
Treat as a targeted legacy exposure check. It becomes urgent if internet-facing Gopher services still exist or the daemon can read sensitive business, credential, or configuration files.
Technical view
The provided sources identify UMN gopher and gopher+ versions 1.12 and 2.0x as vulnerable to unauthorized file reads constrained by the daemon’s filesystem access. No CVSS score, CWE, CPE list, patch detail, or exploit evidence is included.
Likely exposure
Exposure is likely limited to legacy systems still running UMN gopher or gopher+ 1.12 or 2.0x. The bundle does not provide CPEs or a complete affected-products list.
Exploitation context
The source bundle does not indicate active exploitation, and KEV status is false. The vulnerability impact is file disclosure from paths the daemon can access, not broader system compromise based on provided evidence.
Researcher notes
Evidence is sparse. The title and description identify affected UMN gopher/gopher+ versions, but the structured affected field is n/a and no patch, CVSS, CWE, or exploit references are provided.
Mitigation direction
- Inventory systems for UMN gopher or gopher+ services.
- Disable any unnecessary legacy Gopher daemon.
- Check vendor or maintainer guidance for available fixes.
- Restrict the daemon account’s filesystem permissions.
- Isolate required legacy services from untrusted networks.
Validation and detection
- Confirm whether any Gopher service is running or externally reachable.
- Verify product and version against UMN gopher/gopher+ 1.12 and 2.0x.
- Review daemon user permissions for sensitive file access.
- Inspect logs for unusual file access attempts.
- Document any required legacy exception and compensating controls.
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-0124 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-0124CVE 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.