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-2017-7847

Mozilla: Local path string can be leaked from RSS feed

Overview

Published
11 Jun 2018
Modified
17 Jun 2026
Medium CVE
0 Registry packages
4 OS packages
5 Linux distributions
Yes Fix available

Description

Crafted CSS in an RSS feed can leak and reveal local path strings, which may contain user name. This vulnerability affects Thunderbird < 52.5.2.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Weakness: CWE-200

Affected packages · 0

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

Operating systems · 9 fixes

Oracle Linux 1 release · 1 package

fixed 1
thunderbird
Oracle Linux fixes for CVE-2017-7847
ReleasePackageFixed in
7 thunderbird 52.5.2-1.0.1.el7_4

Red Hat 1 release · 1 package

fixed 1
thunderbird
Red Hat fixes for CVE-2017-7847
ReleasePackageFixed inAdvisory
7 thunderbird 0:52.5.2-1.el7_4 RHSA-2018:0061

debian 5 releases · 1 package

fixed 5
thunderbird
debian fixes for CVE-2017-7847
ReleasePackageFixed in
11 thunderbird 1:52.5.2-1
12 thunderbird 1:52.5.2-1
13 thunderbird 1:52.5.2-1
14 thunderbird 1:52.5.2-1
9 thunderbird 1:52.5.2-2~deb9u1

echo 1 release · 1 package

fixed 1
thunderbird
echo fixes for CVE-2017-7847
ReleasePackageFixed in
thunderbird 1:52.5.2-1

openSUSE 1 release · 1 package

fixed 1
mozillathunderbird
openSUSE fixes for CVE-2017-7847
ReleasePackageFixed inAdvisory
Tumbleweed mozillathunderbird +2 91.1.1-1.1 openSUSE-SU-2024:10601-1

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.