CVE-2017-5380: Use After Free
A potential use-after-free found through fuzzing during DOM manipulation of SVG content.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/firefoxto a version that resolves this vulnerability.Fixed in 118.0.2-1 - Upgrade
Upgrade
debian/firefox-esrto a version that resolves this vulnerability.Fixed in 91.12.0esr-1~deb10u1Fixed in 115.3.1esr-1~deb10u1Fixed in 102.15.0esr-1~deb11u1Fixed in 115.3.1esr-1~deb11u1Fixed in 102.15.1esr-1~deb12u1Fixed in 115.3.0esr-1~deb12u1Fixed in 115.3.0esr-1Fixed in 115.4.0esr-1 - Upgrade
Upgrade
Thunderbirdto a version that resolves this vulnerability.Fixed in 45.7 - Upgrade
Upgrade
Firefoxto a version that resolves this vulnerability.Fixed in 51 - Upgrade
Upgrade
Firefox ESRto a version that resolves this vulnerability.Fixed in 45.7 - Upgrade
Upgrade
alpine/firefox-esrto a version that resolves this vulnerability.Fixed in 45.7.0-r0
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2017-5375
- CVE-2017-5376
- CVE-2017-5378
- CVE-2017-5380
- CVE-2017-5390
- CVE-2017-5396
- CVE-2017-5383
- CVE-2017-5373
- CVE-2017-5377
- CVE-2017-5379
- CVE-2017-5389
- CVE-2017-5381
- CVE-2017-5382
- CVE-2017-5384
- CVE-2017-5385
- CVE-2017-5386
- CVE-2017-5394
- CVE-2017-5391
- CVE-2017-5392
- CVE-2017-5393
- CVE-2017-5395
- CVE-2017-5387
- CVE-2017-5388
- CVE-2017-5374
Frequently Asked Questions
What is the severity of CVE-2017-5380?
CVE-2017-5380 is classified as a medium severity vulnerability.
How do I fix CVE-2017-5380?
To fix CVE-2017-5380, upgrade to Thunderbird version 45.7, Firefox ESR version 45.7, or Firefox version 51 or later.
What software is affected by CVE-2017-5380?
CVE-2017-5380 affects Thunderbird versions below 45.7, Firefox ESR versions below 45.7, and Firefox versions below 51.
What type of vulnerability is CVE-2017-5380?
CVE-2017-5380 is a use-after-free vulnerability that arises during DOM manipulation of SVG content.
Is there a workaround for CVE-2017-5380?
There are no known workarounds for CVE-2017-5380; updating to a secure version is recommended.