CVE-2011-3667
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 User.offer_account_by_email WebService method in Bugzilla 2.x and 3.x before 3.4.13, 3.5.x and 3.6.x before 3.6.7, 3.7.x and 4.0.x before 4.0.3, and 4.1.x through 4.1.3, when createemailregexp is not empty, does not properly handle user_can_create_account settings, which allows remote attackers to create user accounts by leveraging a token contained in an e-mail message.
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 User.offer_account_by_email WebService method in Bugzilla fails to properly enforce the user_can_create_account permission when the createemailregexp configuration option is set. This authorization bypass allows remote attackers to create user accounts by exploiting tokens embedded in invitation email messages, bypassing intended access controls.
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.0= 2.2= 2.4= 2.6= 2.8= 2.9= 2.10= 2.12= 2.14= 2.14.1= 2.14.2= 2.14.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify Bugzilla installation and versionCheck the Bugzilla version by examining the VERSION file in the Bugzilla root directory, or run: `perl -MBugzilla -e 'print Bugzilla->VERSION . "\n"'` from the Bugzilla directoryAffected if The installed version is one of: 2.0, 2.2, 2.4, 2.6, 2.8, 2.9, 2.10, 2.12, 2.14, 2.14.1, 2.14.2, or 2.14.3
-
Verify WebService is accessibleCheck if the WebService interface is enabled by examining the 'webservice' parameter in the Bugzilla administration panel under Parameters, or by checking the localconfig database for 'webservice' settingAffected if The WebService (xmlrpc.cgi) is enabled and accessible from the network
-
Inspect createemailregexp configurationLog in as an administrator, go to Administration > Parameters > Email, and check the 'createemailregexp' field; alternatively, query the 'params' table in the Bugzilla database for the 'createemailregexp' valueAffected if The createemailregexp configuration option is populated with a regular expression pattern (not blank or empty)
-
Confirm user_can_create_account permission statusCheck the Bugzilla group permissions for the WebService user or the default 'can_create_account' permission setting in Administration > Parameters > User AuthenticationAffected if The user_can_create_account permission may not be properly enforced for the WebService method in affected versions
You are affected if running Bugzilla versions 2.0 through 2.14.3 AND the WebService is enabled AND createemailregexp is configured, as the User.offer_account_by_email method can be exploited to bypass the user_can_create_account permission check.
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 versions 3.4.13, 3.6.7, 4.0.3, or 4.1.4 and later which contain the patched code. Alternatively, ensure createemailregexp is not configured unless account creation is intentionally allowed for the WebService.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3667 — 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-2011-3667 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