Security readout for executives and security teams
Plain-English summary
This old Docview issue can let a remote user read files that the server itself exposes as publicly readable. The business risk is mainly legacy estate risk: forgotten Caldera, SCO Linux, or OpenServer systems with Docview and Apache reachable from a network.
Executive priority
Prioritize if the organization still operates SCO, Caldera, or OpenServer systems. For most modern environments, urgency depends on whether these legacy platforms remain reachable.
Technical view
Docview before 1.1-18 on Caldera OpenLinux 3.1.1, SCO Linux 4.0, and OpenServer 5.0.7 configures Apache in a way that permits arbitrary publicly readable file disclosure via a crafted URL, possibly involving rewrite rules.
Likely exposure
Likely exposure is limited to legacy hosts running the named Docview and operating system combinations with the Apache web interface reachable by users or the internet.
Exploitation context
The source bundle does not include CVSS, CWE, proof of exploitation, or KEV listing. Treat active exploitation as unconfirmed based on the provided evidence.
Researcher notes
Evidence is sparse and old. The CVE describes file disclosure through Apache configuration, possibly rewrite rules, but does not provide CVSS, CWE, detailed affected CPEs, exploit status, or full remediation instructions.
Mitigation direction
- Inventory legacy Caldera, SCO Linux, and OpenServer systems for Docview.
- Check whether Docview is older than 1.1-18.
- Apply vendor guidance or update to a non-vulnerable Docview version if available.
- Restrict network access to affected Apache/Docview services until remediated.
- Review Apache rewrite and Docview exposure against vendor configuration guidance.
Validation and detection
- Confirm no reachable host runs Docview before 1.1-18.
- Verify affected Apache/Docview endpoints are not internet-accessible.
- Review web logs for unusual Docview file access patterns.
- Confirm remediation with asset inventory and configuration review.
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-2003-0658 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-2003-0658CVE 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.