Bug 592492 (CVE-2010-1628) - CVE-2010-1628 ghostscript: internal stack overflow due to recursive calls
Summary: CVE-2010-1628 ghostscript: internal stack overflow due to recursive calls
Alias: CVE-2010-1628
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://bugs.ghostscript.com/show_bug....
Depends On: 614945 614946
TreeView+ depends on / blocked
Reported: 2010-05-14 22:51 UTC by Vincent Danen
Modified: 2021-02-24 23:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-02-14 13:55:58 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Ghostscript 691295 0 None None None Never

Description Vincent Danen 2010-05-14 22:51:21 UTC
The following vulnerability was reported to Ubuntu's bug tracker [1] by Dan Rosenberg:

1. The Ghostscript interpreter fails to properly handle some cases of infinite recursion. By creating a .ps file with a sequence such as:

/A{pop 0 A 0} bind def
/product A 0

The interpreter's internal stack will be overflowed with recursive calls. Rather than gracefully handling this situation, the interpreter continues execution by jumping to an (usually invalid) address near (or past) the tail end of the stack. Without further manipulation, this would simply result in a segfault, but it turns out that by altering the number of variable definitions that occur before the call to the infinitely recursive procedure, the user can actually exert control over the address that is jumped to. Combined with the fact that the attacker has an easy way to introduce shellcode (via the .ps file), this can definitely result in arbitrary code execution. I have not developed a fully functional exploit for this case, but the attached reproducer ("infinite.ps") will trigger a segfault in the same location on all of the versions of Ghostscript I have tested, including 8.61, 8.62, 8.64, and 8.70. If you wish to more convincingly verify that this is exploitable, place varying amounts of "/A{ 0 } bind def" strings at the beginning of the file, and observe how the EIP at crash time is altered. Unfortunately, the Ghostscript code is rather complex, so I am unable to determine the root cause of this vulnerability in the source.

Reproducers are available from the noted bug report.  This was reported to Ubuntu in conjunction with the CVE-2010-1869, but it does not have a CVE name as far as I can see.

[1] https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/546009

Comment 1 Vincent Danen 2010-05-14 22:52:54 UTC
Reported to full-disclosure here:


Comment 3 Vincent Danen 2010-05-19 03:00:11 UTC
This is CVE-2010-1628.

Comment 4 Tomas Hoger 2010-05-19 14:45:57 UTC
Adding link to upstream bug as comment, URL is easy to miss:

Comment 5 Tomas Hoger 2010-07-15 15:36:11 UTC
According to upstream bug, this issue was introduced in upstream revision r7694:


Code changed in r7694 was first introduced in r6706:


This change is not included in ghostscript packages in Red Hat Enterprise Linux 3, 4 and 5.

Upstream fix to correct PostScript stack overflow causing memory corruption:



Not vulnerable. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 3, 4, or 5.

Comment 7 Tomas Hoger 2010-07-15 15:40:21 UTC
Created ghostscript tracking bugs for this issue

Affects: fedora-all [bug 614946]

Comment 8 Kenichi Takemura 2010-08-03 04:26:02 UTC

$ rpm -q ghostscript

Both of following executions do not crash ghostscript.

$ gs infinite.ps
$ gs overflow.ps

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