Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1626481 (CVE-2018-16648) - CVE-2018-16648 mupdf: Array index underflow in pdf_dev_alpha resulting in a crash
Summary: CVE-2018-16648 mupdf: Array index underflow in pdf_dev_alpha resulting in a c...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2018-16648
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1626484
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-07 12:53 UTC by Andrej Nemec
Modified: 2019-09-29 14:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:37:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrej Nemec 2018-09-07 12:53:46 UTC
In Artifex MuPDF 1.13.0, the fz_append_byte function in fitz/buffer.c allows remote attackers to cause a denial of service (segmentation fault) via a crafted pdf file. This is caused by a pdf/pdf-device.c pdf_dev_alpha array-index underflow.

Upstream issue:

https://bugs.ghostscript.com/show_bug.cgi?id=699685

Comment 1 Andrej Nemec 2018-09-07 12:56:17 UTC
Created mupdf tracking bugs for this issue:

Affects: fedora-all [bug 1626484]

Comment 2 Dhananjay Arunesh 2019-03-12 05:43:59 UTC
Upstream commit:
http://git.ghostscript.com/?p=mupdf.git;h=38f883fe129a5e89306252a4676eaaf4bc968824

Comment 3 Product Security DevOps Team 2019-06-10 10:37:37 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


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