Bug 917111 - (CVE-2013-1790) CVE-2013-1790 poppler: uninitialized memory read flaw
CVE-2013-1790 poppler: uninitialized memory read flaw
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20130109,reported=2...
: Security
Depends On: 917113
Blocks: 917112
  Show dependency treegraph
 
Reported: 2013-03-01 13:13 EST by Vincent Danen
Modified: 2015-08-22 02:51 EDT (History)
2 users (show)

See Also:
Fixed In Version: poppler 0.22.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-22 02:51:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Vincent Danen 2013-03-01 13:13:18 EST
An uninitialized memory read flaw was reported in poppler (fixed in version 0.22.1):

Initialize refLine totally
Fixes uninitialized memory read in 1004.pdf.asan.7.3  [1]

[1] http://cgit.freedesktop.org/poppler/poppler/commit/?h=poppler-0.22&id=b1026b5978c385328f2a15a2185c599a563edf91
Comment 1 Vincent Danen 2013-03-01 13:17:17 EST
Created poppler tracking bugs for this issue

Affects: fedora-all [bug 917113]
Comment 2 Fedora Update System 2013-03-13 22:44:56 EDT
poppler-0.20.2-10.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 3 Fedora Update System 2013-03-13 22:47:57 EDT
poppler-0.18.4-4.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Huzaifa S. Sidhpurwala 2013-04-30 00:07:55 EDT
This issue affects the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6.
Comment 7 Vincent Danen 2015-08-22 02:51:09 EDT
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.