Bug 2235001 (CVE-2020-21710) - CVE-2020-21710 ghostscript: Divide by zero in eps_print_page in gdevepsn.c
Summary: CVE-2020-21710 ghostscript: Divide by zero in eps_print_page in gdevepsn.c
Keywords:
Status: NEW
Alias: CVE-2020-21710
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2235004 2235005 2235009 2235268
Blocks: 2235003
TreeView+ depends on / blocked
 
Reported: 2023-08-25 21:22 UTC by Pedro Sampaio
Modified: 2024-05-22 09:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
GhostScript is vulnerable to divide by zero issue in function eps_print_page in gdevepsn.c allows remote attacker to cause a denial of service via crafted PDF file.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:2966 0 None None None 2024-05-22 09:23:23 UTC

Description Pedro Sampaio 2023-08-25 21:22:51 UTC 
A divide by zero issue discovered in eps_print_page in gdevepsn.c in Artifex Software GhostScript 9.50 allows remote attackers to cause a denial of service via opening of crafted PDF file.

References:

https://bugs.ghostscript.com/show_bug.cgi?id=701843
https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=4e713293de84b689c4ab358f3e110ea54aa81925
Comment 3 TEJ RATHI 2023-08-28 08:54:19 UTC 
Created ghostscript tracking bugs for this issue:

Affects: fedora-all [bug 2235268]
Comment 4 Michael J Gruber 2023-12-09 16:26:34 UTC 
This bug was fixed in gs 9.51, and we have had gs 9.52 in Fedora 33 3 years ago already. What is the point of filing this against fedora_all now in 2023? Just for churns?
Comment 6 errata-xmlrpc 2024-05-22 09:23:22 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:2966 https://access.redhat.com/errata/RHSA-2024:2966
Note You need to log in before you can comment on or make changes to this bug.