dbcve.org
BrowseridDrupal extension · Browserid Project

CVE-2012-2714

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The BrowserID (Mozilla Persona) module 7.x-1.x before 7.x-1.3 for Drupal allows remote attackers to hijack the authentication of arbitrary users via the audience identifier.

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 confidence

The BrowserID (Mozilla Persona) authentication module for Drupal 7.x before 7.x-1.3 contains a flaw in audience identifier validation. The audience field in BrowserID tokens is used to verify the token is intended for the correct site; the vulnerability allows attackers to manipulate this value to hijack authentication sessions for arbitrary users.

MitigationUpgrade the Drupal BrowserID module to version 7.x-1.3 or later, which contains the corrected audience validation logic.

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
BrowseridDrupal extension
Affected:= 7.x-1.0= 7.x-1.1= 7.x-1.2

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the BrowserID module installation
    Check for the presence of the browserid module directory in your Drupal installation, typically under /sites/all/modules/ or /modules/. Look for a folder named 'browserid' or 'persona'.
    Affected if The browserid module directory exists on the server.
  2. Determine the installed BrowserID module version
    Open the browserid.info file (or browserid.module) within the browserid module directory and look for the version line, such as 'version = 7.x-1.x' or similar. Compare this version to the affected versions: 7.x-1.0, 7.x-1.1, or 7.x-1.2.
    Affected if The version is 7.x-1.0, 7.x-1.1, or 7.x-1.2.
  3. Verify if the BrowserID module is enabled
    Query the Drupal system table using SQL: SELECT status FROM system WHERE name = 'browserid'; Or use Drush: drush pm-list --status=enabled | grep browserid.
    Affected if The module status is enabled (status = 1).
  4. Inspect the audience validation logic
    Examine the file containing the BrowserID assertion validation, typically browserid.module or a dedicated validation include file. Look for the code that processes the 'audience' or 'aud' claim from the BrowserID token. In vulnerable versions, this validation may not properly verify the audience matches the current site.
    Affected if The module uses audience validation code from versions 7.x-1.0 through 7.x-1.2 without the fix that properly validates the audience claim.

You are affected if the BrowserID module is installed with version 7.x-1.0, 7.x-1.1, or 7.x-1.2 and the module is enabled, allowing potentially malicious actors to manipulate the audience field in BrowserID tokens to hijack user authentication sessions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Drupal BrowserID module to version 7.x-1.3 or later, which contains the corrected audience validation logic.

Recommended fix High confidence

BrowserID module 7.x-1.3 for Drupal 7.x

  1. 1. Backup your Drupal database and files before making any changes.
  2. 2. Navigate to the Drupal administration panel for module management.
  3. 3. Uninstall the current BrowserID (Mozilla Persona) module version (7.x-1.0, 7.x-1.1, or 7.x-1.2).
  4. 4. Download the BrowserID module version 7.x-1.3 from the official Drupal repository at drupal.org/project/browserid.
  5. 5. Extract and install the 7.x-1.3 version of the module.
  6. 6. Enable the updated BrowserID module in the Drupal modules administration.
  7. 7. Clear the Drupal cache to ensure the new module files are loaded.
  8. 8. Verify the module is running version 7.x-1.3 in the modules list.
Caveat Review the module's release notes for 7.x-1.3 for any configuration changes required for the audience identifier parameter.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Browserid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2714 — 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-2012-2714 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