CVE-2013-1670

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 21.0, Firefox ESR 17.x before 17.0.6, Thunderbird before 17.0.6, and Thunderbird ESR 17.x before 17.0.6 does not prevent acquisition of chrome privileges during calls to content level constructors, which allows remote attackers to bypass certain read-only restrictions and conduct cross-site scripting (XSS) attacks via a crafted web site.

Additional information

  • Bugzilla 962596: Mozilla: Privileged access for content level constructor (MFSA 2013-42)
  • FAQ: Frequently asked questions about CVE-2013-1670

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

4.3

4.3

Attack Vector

Network

Network

Access Complexity

Medium

Medium

Authentication

None

None

Confidentiality Impact

None

None

Integrity Impact

Partial

Partial

Availability Impact

None

None

CVSS v2 Vector

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

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

Acknowledgements

Red Hat would like to thank Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter.

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.