dbcve.org
BugzillaApplication · Mozilla

CVE-2010-1204

MEDIUM · 5.0 CVSS v2.0 Published 2010-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Search.pm in Bugzilla 2.17.1 through 3.2.6, 3.3.1 through 3.4.6, 3.5.1 through 3.6, and 3.7 allows remote attackers to obtain potentially sensitive time-tracking information via a crafted search URL, related to a "boolean chart search."

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 confidence

Information disclosure vulnerability in Bugzilla's Search.pm where a crafted boolean chart search URL allows remote unauthenticated attackers to access sensitive time-tracking data that should be restricted. The vulnerability exists across multiple version branches (2.17.1-3.2.6, 3.3.1-3.4.6, 3.5.1-3.7).

MitigationUpgrade Bugzilla to a version beyond the affected releases that includes the patched Search.pm with proper access controls on time-tracking data in search results, or implement URL filtering to block boolean chart search parameters that could expose time-tracking fields.

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
BugzillaApplication
Affected:= 2.17.1= 2.17.3= 2.17.4= 2.17.5= 2.17.6= 2.17.7= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Bugzilla version
    Check the version file in your Bugzilla installation (typically 'Bugzilla/Version.pm' or run 'perl -MBugzilla -e 'print Bugzilla::VERSION'' from the Bugzilla directory)
    Affected if The version number falls within 2.17.1-3.2.6, 3.3.1-3.4.6, or 3.5.1-3.7
  2. Locate Search.pm file
    Find the Search.pm file in your Bugzilla installation, typically under 'Bugzilla/Search.pm'
    Affected if The file exists and corresponds to a vulnerable version from step 1
  3. Verify time-tracking is enabled
    Check Bugzilla's parameters configuration (via 'editparams.cgi' or the 'params' table in the database) for the 'timetrackinggroup' parameter - if it is set to any group, time-tracking data exists in the system
    Affected if Time-tracking is enabled and the 'timetrackinggroup' parameter is configured
  4. Test for boolean chart search exposure
    Attempt to access a crafted URL with boolean chart parameters that reference time-tracking fields (such as 'work_time', 'remaining_time', or 'percentage_complete') without authentication, for example: query?type=boolean&field0=work_time
    Affected if The request returns time-tracking data without requiring authentication or proper group membership verification
  5. Inspect Search.pm for access control code
    Examine the Search.pm file for the 'Chart' or 'booleanchart' subroutines and verify whether they properly check group permissions before returning time-tracking fields (look for calls to 'Bugzilla->user->can_see_time_trackee' or similar group validation)
    Affected if The Search.pm code lacks proper group membership checks before exposing time-tracking fields in search results

If Bugzilla version is in the affected range AND time-tracking is enabled AND unauthenticated boolean chart queries can return time-tracking data without group verification, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Bugzilla to a version beyond the affected releases that includes the patched Search.pm with proper access controls on time-tracking data in search results, or implement URL filtering to block boolean chart search parameters that could expose time-tracking fields.

Fix this in Bugzilla Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-1204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-1204 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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