CVE-2012-4196

Public on

Last Modified: UTC

CriticalCritical ImpactWhat does this mean?

Insights vulnerability analysis

View exposed systems

Description

The CVE Program describes this issue as:

Mozilla Firefox before 16.0.2, Firefox ESR 10.x before 10.0.10, Thunderbird before 16.0.2, Thunderbird ESR 10.x before 10.0.10, and SeaMonkey before 2.13.2 allow remote attackers to bypass the Same Origin Policy and read the Location object via a prototype property-injection attack that defeats certain protection mechanisms for this object.

Additional information

  • Bugzilla 869893: Mozilla: Fixes for Location object issues (MFSA 2012-90)
  • FAQ: Frequently asked questions about CVE-2012-4196

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

6.8

6.4

Attack Vector

Network

Network

Access Complexity

Medium

Low

Authentication

None

None

Confidentiality Impact

Partial

Partial

Integrity Impact

Partial

Partial

Availability Impact

Partial

None

CVSS v2 Vector

Red Hat: AV:N/AC:M/Au:N/C:P/I:P/A:P

NVD: AV:N/AC:L/Au:N/C:P/I:P/A:N

Acknowledgements

Red Hat would like to thank Mozilla project for reporting this issue.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.