CVE-2017-14519
poppler: Memory corruption via Gfx.cc infinite loop
Overview
Description
In Poppler 0.59.0, memory corruption occurs in a call to Object::streamGetChar in Object.h after a repeating series of Gfx::display, Gfx::go, Gfx::execOp, Gfx::opShowText, and Gfx::doShowText calls (aka a Gfx.cc infinite loop).
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-835
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 9 fixes
Red Hat 1 release · 1 package
wont fix 1
poppler
| Release | Package | Fixed in |
|---|---|---|
| 7 | poppler +9 | wont fix |
debian 5 releases · 1 package
fixed 5
poppler
| Release | Package | Fixed in |
|---|---|---|
| 11 | poppler | 0.61.1-2 |
| 12 | poppler | 0.61.1-2 |
| 13 | poppler | 0.61.1-2 |
| 14 | poppler | 0.61.1-2 |
| 9 | poppler | 0.48.0-2+deb9u1 |
echo 1 release · 1 package
fixed 1
poppler
| Release | Package | Fixed in |
|---|---|---|
| poppler | 0.61.1-2 |
root.io debian 1 release · 1 package
fixed 1
rootio-poppler
| Release | Package | Fixed in |
|---|---|---|
| 12 | rootio-poppler | 0.61.1-2 |
seal Red Hat 1 release · 1 package
fixed 1
poppler
| Release | Package | Fixed in |
|---|---|---|
| 7 | poppler +1 | 0.26.5-43.el7.1+sp999 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2017-14519
- bugs.freedesktop.org https://bugs.freedesktop.org/show_bug.cgi?id=102701
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2017-14519
- ubuntu.com https://ubuntu.com/security/notices/USN-3433-1
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2017-14519
- www.debian.org https://www.debian.org/security/2018/dsa-4079
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.