CVE-2002-0811
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.14 before 2.14.2, and 2.16 before 2.16rc2, may allow remote attackers to cause a denial of service or execute certain queries via a SQL injection attack on the sort order parameter to buglist.cgi.
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 · high confidenceBugzilla versions 2.14 before 2.14.2 and 2.16 before 2.16rc2 contain a SQL injection vulnerability in the sort order parameter of buglist.cgi. Attackers can inject arbitrary SQL commands through this parameter, potentially causing denial of service or executing unauthorized database queries.
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.14= 2.14.1= 2.16CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate Bugzilla installationSearch for buglist.cgi file in the web server's document root or cgi-bin directory. Common paths include /var/www/html/buglist.cgi or /cgi-bin/buglist.cgi.Affected if buglist.cgi file exists on the server
-
Identify Bugzilla versionCheck the Bugzilla version file (VERSION or Bugzilla/Config.pm) in the Bugzilla directory, or access the Bugzilla admin pages which display the version number.Affected if Version displayed is 2.14, 2.14.1, or 2.16
-
Confirm vulnerable version rangeCompare the installed version against the affected range: versions 2.14, 2.14.1, and 2.16 are vulnerable. Versions 2.14.2 and 2.16rc2 and later are patched.Affected if Installed version is exactly 2.14, 2.14.1, or 2.16 without any patches applied
-
Verify buglist.cgi is web-accessibleAttempt to access http://[server]/buglist.cgi or the equivalent path via HTTP request. A successful response indicates the CGI script is accessible.Affected if buglist.cgi responds to HTTP requests, making the SQL injection vector reachable
A system is affected if Bugzilla versions 2.14, 2.14.1, or 2.16 are installed with buglist.cgi accessible via web and the sort order parameter accepts unsanitized user input.
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 2.14.2 or 2.16rc2 or later, which contain proper input sanitization for the sort order parameter. If immediate upgrade is not feasible, apply a web application firewall (WAF) rule to block SQL injection attempts in buglist.cgi parameters.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0811 — 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-2002-0811 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