CVE-2002-0010: Affected product: security vulnerability

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

Bugzilla before 2.14.1 allows remote attackers to inject arbitrary SQL code and create files or gain privileges via (1) the sql parameter in buglist.cgi, (2) invalid field names from the "boolean chart" query in buglist.cgi, (3) the mybugslink parameter in userprefs.cgi, (4) a malformed bug ID in the buglist parameter in long_list.cgi, and (5) the value parameter in editusers.cgi, which allows groupset privileges to be modified by attackers with blessgroupset privileges.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Unspecified
Privileges required: None: unauthenticated exploitation is possible
User interaction: Not stated in the selected CVSS metric
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Not stated in the selected CVSS metric
Weakness ? CWE means Common Weakness Enumeration.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: AV:N/AC:L/Au:N/C:P/I:P/A:P
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

Unauthenticated

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2002-0010Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: n/a: n/a
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 10 Jan 2002 · Last source change 8 Aug 2024, 02:35 UTC · CWE not yet assigned

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-13

European sourceENISA EUVD · EUVD-2002-0010

Product sourceUnavailable

Remediation sourceCVE/CNA references

CWE sourceUnavailable

NVD statusNVD modified after enrichment

Missing structured fields: CWE classification, affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

13 Sep 2026, 17:01 UTC
ENISA EUVD mappingEUVD-2002-0010 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2002-0010"}
ENISA EUVD ↗
8 Aug 2024, 02:35 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: archives.neohapsis.com/0034.html; added remediation: archives.neohapsis.com/0034.html; removed vendor advisory: rhn.redhat.com/RHSA-2002-001.html.
Before
vendor advisory: rhn.redhat.com/RHSA-2002-001.html
After
patch: archives.neohapsis.com/0034.html · remediation: archives.neohapsis.com/0034.html
archives.neohapsis.com ↗
8 Aug 2024, 02:35 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
n/a: n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
n/a: n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
8 Aug 2024, 02:35 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
archives.neohapsis.com ↗
8 Aug 2024, 02:35 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
8 Aug 2024, 02:35 UTC
CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 2.0 · NIST NVD · AV:N/AC:L/Au:N/C:P/I:P/A:P).
Before
not recorded
After
7.5 (CVSS 2.0 · NIST NVD · AV:N/AC:L/Au:N/C:P/I:P/A:P)
NIST NVD ↗
8 Aug 2024, 02:35 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2002-01-10CVE published

2024-08-08Fixed release or patch reference recorded

ENISA EUVD · EUVD-2002-0010↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Affected product: security vulnerability

Published severity in operational context

Evidence used

Compensating controls

Verification

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2002-0010