Bug 1870229 (CVE-2020-16294) - CVE-2020-16294 ghostscript: buffer overflow in epsc_print_page() in devices/gdevepsc.c could result in a DoS
Summary: CVE-2020-16294 ghostscript: buffer overflow in epsc_print_page() in devices/g...
Alias: CVE-2020-16294
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1870232 1872066 1872067
Blocks: 1870273
TreeView+ depends on / blocked
Reported: 2020-08-19 15:11 UTC by Michael Kaplan
Modified: 2021-05-18 20:35 UTC (History)
7 users (show)

Fixed In Version: ghostscript 9.51
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-18 20:35:22 UTC

Attachments (Terms of Use)

Description Michael Kaplan 2020-08-19 15:11:29 UTC
A buffer overflow vulnerability in epsc_print_page() in devices/gdevepsc.c of Artifex Software GhostScript v9.50 allows a remote attacker to cause a denial of service via a crafted PDF file. This is fixed in v9.51.



Comment 1 Michael Kaplan 2020-08-19 15:14:41 UTC
Created ghostscript tracking bugs for this issue:

Affects: fedora-all [bug 1870232]

Comment 4 Todd Cullum 2020-08-24 23:25:27 UTC
Flaw summary:

This flaw is an out-of-bounds read of global variables graphics_modes_9 and graphics_modes_24, which occurs in the epsc_print_page() routine in /devices/gdevepsc.c. the arrays are indexed like: graphics_modes_9[x_dpi / 60]. If x_dpi (which is parsed from the input file) is too large. x_dpi is set as (int)pdev->x_pixels_per_inch. The patch establishes a max_dpi and checks x_dpi against it to error out and avoid this flaw.

Comment 5 errata-xmlrpc 2021-05-18 15:36:56 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:1852 https://access.redhat.com/errata/RHSA-2021:1852

Comment 6 Product Security DevOps Team 2021-05-18 20:35:22 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


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