LiveActive security incident?Get immediate response
CVE Record

CVE-2005-2174: Bugzilla 2.17.x, 2.18 before 2.18.2, 2.19.x, and 2.20 before 2.20rc1 inserts a bug into the database before...

Bugzilla 2.17.x, 2.18 before 2.18.2, 2.19.x, and 2.20 before 2.20rc1 inserts a bug into the database before it is marked private, which introduces a race condition and allows attackers to access information about the bug via buglist.cgi before MySQL replication is complete.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This older Bugzilla flaw could briefly expose information from bugs intended to be private. The issue is a race condition during bug creation, where a bug enters the database before its private status is fully applied. Business impact is mainly accidental or targeted disclosure of sensitive vulnerability, product, or customer issue details. Exposure is likely limited to organizations still running the named legacy Bugzilla versions, especially where private bugs and MySQL replication are used. Modern deployments are unlikely to be affected unless they retain old, unsupported Bugzilla instances. Prioritize remediation if any legacy Bugzilla instance is still used for vulnerability reports, customer issues, or confidential engineering work. The flaw is old and no active exploitation is cited, but disclosure of private bug data can create meaningful business and security risk. Mitigation focus: Upgrade Bugzilla 2.18 deployments to 2.18.2 or later.; Upgrade 2.20 pre-release deployments to 2.20rc1 or later.; Move off affected 2.17.x and 2.19.x development releases..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2005-2174 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.