Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-7175

Mozilla: Vulnerabilities found through code inspection (MFSA 2015-112)

Overview

Published
24 Sep 2015
Modified
6 May 2026
High CVE
0 Registry packages
18 OS packages
3 Linux distributions
Yes Fix available

Description

The XULContentSinkImpl::AddText function in Mozilla Firefox before 41.0 and Firefox ESR 38.x before 38.3 might allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly have unspecified other impact via unknown vectors, related to an "overflow."

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 6 fixes

Oracle Linux 1 release · 1 package

fixed 1
thunderbird
Oracle Linux fixes for CVE-2015-7175
ReleasePackageFixed in
7 thunderbird 38.3.0-1.0.1.el7_1

Red Hat 1 release · 2 packages

fixed 2
thunderbird firefox
Red Hat fixes for CVE-2015-7175
ReleasePackageFixed inAdvisory
7 thunderbird 0:38.3.0-1.el7_1 RHSA-2015:1852
7 firefox 0:38.3.0-2.el7_1 RHSA-2015:1834

openSUSE 1 release · 3 packages

fixed 3
seamonkey mozillathunderbird mozillafirefox
openSUSE fixes for CVE-2015-7175
ReleasePackageFixed inAdvisory
Tumbleweed seamonkey +4 2.40-6.1 openSUSE-SU-2024:10218-1
Tumbleweed mozillathunderbird +4 45.5.1-1.1 openSUSE-SU-2024:10230-1
Tumbleweed mozillafirefox +5 50.1.0-1.1 openSUSE-SU-2024:10071-1

References

Show all 28 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.