FirefoxWeb browser · Mozilla

CVE-2012-1955

MEDIUM · 6.8 CVSS v2.0 Published 2012-07-18

Fix available

A fix is available. Upgrade to after 2.10 or later.

See remediation →

77/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Mozilla Firefox 4.x through 13.0, Firefox ESR 10.x before 10.0.6, Thunderbird 5.0 through 13.0, Thunderbird ESR 10.x before 10.0.6, and SeaMonkey before 2.11 allow remote attackers to spoof the address bar via vectors involving history.forward and history.back calls.

Technical summary

dbcve analysis · high confidence

Address bar spoofing vulnerability in Mozilla Firefox 4.x-13.0, Firefox ESR 10.x before 10.0.6, Thunderbird 5.0-13.0, Thunderbird ESR 10.x before 10.0.6, and SeaMonkey before 2.11 allows remote attackers to manipulate the displayed URL using history.forward and history.back JavaScript calls, potentially tricking users into believing they are on a different website than the one actually loaded.

MitigationUpdate affected Mozilla products to the latest patched versions (Firefox 14+, Firefox ESR 10.0.6+, Thunderbird 14+, SeaMonkey 2.11+) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:= 4.0= 4.0.1= 5.0= 5.0.1= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 8.0.1= 9.0

ThunderbirdApplication

Affected:= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 9.0= 9.0.1= 10.0= 10.0.1= 10.0.2

Thunderbird EsrApplication

Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.0.5

SeamonkeyApplication

Affected:<= 2.10= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1

CVSS breakdown

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?

dbcve checks

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

Identify installed Mozilla product

Open the application and check Help > About, or check the executable properties. For Firefox, look for firefox.exe. For Thunderbird, look for thunderbird.exe. For SeaMonkey, look for seamonkey.exe.

Affected if The installed application is Firefox, Thunderbird, or SeaMonkey
Determine Firefox version

In Firefox, type 'about:support' in the address bar or go to Help > About Firefox. The version number is displayed on that page.

Affected if Version is 4.0 through 13.0 inclusive, or ESR 10.x before 10.0.6
Determine Thunderbird version

In Thunderbird, go to Help > About Thunderbird. The version number is displayed on that page.

Affected if Version is 5.0 through 13.0 inclusive, or ESR 10.0 through 10.0.5
Determine SeaMonkey version

In SeaMonkey, go to Help > About SeaMonkey. The version number is displayed on that page.

Affected if Version is 2.10 or lower, or any 1.x version through 1.1
Verify JavaScript is enabled

The vulnerability requires JavaScript to be enabled in the browser. Check Tools > Options > Content (Firefox) or Options > Privacy & Security > Permissions (newer versions) to see if JavaScript is allowed.

Affected if JavaScript is enabled and the product version falls within the affected ranges

The user is affected if they have Firefox 4.0-13.0 or ESR 10.x before 10.0.6, Thunderbird 5.0-13.0 or ESR 10.0-10.0.5, or SeaMonkey 2.10 or lower (including 1.x versions) with JavaScript enabled.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 2.10

Interim mitigation

Update affected Mozilla products to the latest patched versions (Firefox 14+, Firefox ESR 10.0.6+, Thunderbird 14+, SeaMonkey 2.11+) to remediate this vulnerability.

Fix this in Firefox Scoped from the published advisory

Consultation1.0 h
Testing1.0 h
Review / QA1.0 h

3.0 hours of engineering $750

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2012-1955?

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.

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

At a glance

A fix existsUpgrade to after 2.10 or later

Severity 6.8 Medium

Exploit likelihood EPSS, next 30 days 2.3%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 3 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2012-1955 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References