Security readout for executives and security teams
Plain-English summary
This old Bugzilla issue could let a remote user see names of products and components that were meant to be restricted. It is an information disclosure flaw, not described as code execution. Business urgency is mainly for organizations still running very old Bugzilla versions exposed to users or the internet.
Executive priority
Treat as a cleanup priority for legacy systems. Escalate if an affected Bugzilla instance is internet-facing or contains sensitive project names, unreleased product details, or restricted component information.
Technical view
CVE-2002-0803 affects Bugzilla 2.14 before 2.14.2 and 2.16 before 2.16rc2. A direct HTTP request to queryhelp.cgi can display restricted product and component information. The source bundle provides no CVSS score, CWE, proof of exploitation, or detailed vendor advisory.
Likely exposure
Exposure is likely limited to legacy Bugzilla deployments matching the affected versions, especially where queryhelp.cgi is reachable remotely. Modern or upgraded Bugzilla instances are not shown as affected by the provided sources.
Exploitation context
The CVE describes remote access through a direct HTTP request. There is no KEV listing and no cited source in the bundle indicating active exploitation. The practical impact is disclosure of restricted Bugzilla project metadata.
Researcher notes
Source data is thin: no CVSS, CWE, vendor reference, or exploit-status evidence is provided. Analysis is based on the CVE description and version boundaries only. Avoid assuming broader impact beyond restricted product and component disclosure.
Mitigation direction
- Identify any Bugzilla 2.14 or 2.16-era deployments.
- Upgrade Bugzilla 2.14 to 2.14.2 or later.
- Upgrade Bugzilla 2.16 pre-release deployments to 2.16rc2 or later.
- If upgrade status is unclear, check current Bugzilla vendor guidance.
- Restrict external access to legacy Bugzilla until validated.
Validation and detection
- Inventory Bugzilla versions across internet-facing and internal systems.
- Confirm whether queryhelp.cgi is reachable remotely.
- Review access controls for restricted products and components.
- Check logs for unusual requests to queryhelp.cgi.
- Document whether affected versions remain in production.
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-0803 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.