CVE-2010-2758
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBugzilla 2.17.1 through 3.2.7, 3.3.1 through 3.4.7, 3.5.1 through 3.6.1, and 3.7 through 3.7.2 generates different error messages depending on whether a product exists, which makes it easier for remote attackers to guess product names via unspecified use of the (1) Reports or (2) Duplicates page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBugzilla versions 2.17.1 through 3.7.2 expose different error messages when a product exists versus when it does not, allowing unauthenticated remote attackers to enumerate valid product names via the Reports or Duplicates page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2= 2.4= 2.6= 2.8= 2.9= 2.17.1= 2.17.2= 2.17.3= 2.17.4= 2.17.5= 2.17.6= 2.17.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Bugzilla versionLocate the Bugzilla installation and check the version file or admin interface. Common locations include the 'Bugzilla/VERSION' Perl module, a 'version' file in the root directory, or the 'admin' page that displays version info.Affected if The installed version is 2.2, 2.4, 2.6, 2.8, 2.9, or any 2.17.x through 3.7.2 (check against the full affected range)
-
Confirm Reports or Duplicates page is accessibleAttempt to access the 'reports.cgi' or 'duplicates.cgi' page without authentication. This is typically at /bugzilla/reports.cgi or /bugzilla/duplicates.cgi on the web server.Affected if The page loads without requiring login credentials (unauthenticated access is enabled)
-
Test error message variance for product enumerationSend HTTP requests to the Reports or Duplicates page with two different 'product' parameters: one with a known valid product name and one with a random non-existent product name. Compare the error messages returned in the HTTP response body.Affected if The error message for a non-existent product differs noticeably from the error message for an existing product (for example, one explicitly states the product does not exist while the other shows a different error or no error)
-
Inspect HTTP response codes or messagesUse a browser or HTTP tool to submit product parameter queries and capture both the HTTP status codes and any inline error text. Look for differences in wording that reveal product validity.Affected if The application reveals through distinct error text or behavior whether a submitted product name is valid in the system
A user is affected if their Bugzilla version falls within the vulnerable range (2.2 through 3.7.2) AND the Reports or Duplicates page returns different error messages for existing versus non-existing product names, allowing an unauthenticated attacker to enumerate valid product names.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Bugzilla 3.2.8, 3.4.8, 3.6.2, or 3.7.3 or later; alternatively, modify the application to return uniform error messages regardless of product existence.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-2758 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data