What is the CVSS score of CVE-2013-0778?

CVE-2013-0778 has a CVSS 2.0 base score of 9.3 (Critical). CVSS vector: AV:N/AC:M/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 1.6%.

Is there a patch available for CVE-2013-0778?

Yes, a patch is available for CVE-2013-0778. Update the affected software to the latest version immediately.

Firefox CVE-2013-0778

CRITICAL

Out-of-bounds Read (CWE-125)

2013-02-19 security@mozilla.org

Mozilla Denial Of Service Buffer Overflow Information Disclosure RCE Firefox Seamonkey Thunderbird Thunderbird Esr Opensuse Ubuntu Linux

9.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

9.3 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Feb 19, 2013 - 23:55 cve.org

CRITICAL 9.3

DescriptionCVE.org

AnalysisAI

The ClusterIterator::NextCluster function in Mozilla Firefox before 19.0, Thunderbird before 17.0.3, and SeaMonkey before 2.16 allows remote attackers to execute arbitrary code or cause a denial of. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. This Out-of-bounds Read vulnerability could allow attackers to read data from memory outside the intended buffer boundaries.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. The ClusterIterator::NextCluster function in Mozilla Firefox before 19.0, Thunderbird before 17.0.3, and SeaMonkey before 2.16 allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds read) via unspecified vectors. Affected products include: Mozilla Firefox, Mozilla Seamonkey, Mozilla Thunderbird, Mozilla Thunderbird Esr, Opensuse. Version information: before 19.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.