CVE-2010-2757
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 · uneditedThe sudo feature in Bugzilla 2.22rc1 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 does not properly send impersonation notifications, which makes it easier for remote authenticated users to impersonate other users without discovery.
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 confidenceThe sudo feature in Bugzilla versions 2.22rc1 through 3.7.2 fails to send impersonation notifications when authenticated users switch to another user's account via the sudo functionality, allowing attackers to impersonate other users without triggering any alert or audit trail.
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.4= 2.6= 2.8= 2.9= 2.22= 2.22.1= 2.22.3= 2.22.4= 2.22.5= 2.22.6= 2.22.7= 2.23CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Identify installed Bugzilla versionAccess the Bugzilla web interface and navigate to the 'About' page, or check the 'Bugzilla/Config.pm' file for the $VERSION variableAffected if The installed version falls within 2.22rc1 through 3.7.2 (or matches any of the specific versions listed: 2.4, 2.6, 2.8, 2.9, 2.22, 2.22.1, 2.22.3-2.22.7, 2.23)
-
Confirm sudo feature is enabledLog in as an administrator, go to the 'Parameters' (or 'Admin' > 'Parameters') section, and locate the 'sudo' or 'allow-sudo' parameter settingAffected if The sudo feature is turned on or set to 'on' in Bugzilla's parameter configuration
-
Verify impersonation notification settingsIn the Bugzilla administration parameters, locate the 'email' or 'notification' settings and check if there is a specific option for 'sudo' or 'impersonation' notifications that should trigger when a user switches accountsAffected if No sudo/impersonation notification option exists or is configured, or if notifications are not being sent when switching accounts via sudo
You are affected if your Bugzilla version is between 2.22rc1 and 3.7.2 AND the sudo feature is enabled, because impersonation events will not generate any notification or audit trail.
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 Bugzilla to a patched version (3.6.2 or later for the 3.6 branch, 3.7.3 or later for the 3.7 branch, or corresponding patches for other affected branches) that properly sends impersonation notifications when the sudo feature is used.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2757 — 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-2757 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