Bug 2325045 (CVE-2024-46953) - CVE-2024-46953 ghostscript: Path Traversal and Code Execution via Integer Overflow in Ghostscript
Summary: CVE-2024-46953 ghostscript: Path Traversal and Code Execution via Integer Ove...
Keywords:
Status: NEW
Alias: CVE-2024-46953
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2325239 2325240 2325241
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-10 22:01 UTC by OSIDB Bzimport
Modified: 2025-05-14 09:20 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2025:7572 0 None None None 2025-05-14 09:20:04 UTC
Red Hat Product Errata RHSA-2025:4362 0 None None None 2025-04-30 09:07:19 UTC
Red Hat Product Errata RHSA-2025:7422 0 None None None 2025-05-13 11:55:05 UTC
Red Hat Product Errata RHSA-2025:7499 0 None None None 2025-05-13 15:59:49 UTC

Description OSIDB Bzimport 2024-11-10 22:01:21 UTC 
An issue was discovered in base/gsdevice.c in Artifex Ghostscript before 10.04.0. An integer overflow when parsing the filename format string (for the output filename) results in path truncation, and possible path traversal and code execution.
Comment 2 errata-xmlrpc 2025-04-30 09:07:17 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:4362 https://access.redhat.com/errata/RHSA-2025:4362
Comment 3 errata-xmlrpc 2025-05-13 11:55:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:7422 https://access.redhat.com/errata/RHSA-2025:7422
Comment 4 errata-xmlrpc 2025-05-13 15:59:48 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

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