CVE-2011-1782: Buffer Overflow

Published May 13, 2011
·
Updated

Heap-based buffer overflow in the readchanneldata function in file-psp.c in the Paint Shop Pro (PSP) plugin in GIMP 2.6.11 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a PSPCOMPRLE (aka RLE compression) image file that begins a long run count at the end of the image. NOTE: some of these details are obtained from third party information. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4543.

Other sources

Originally Common Vulnerabilities and Exposures assigned an identifier of CVE-2010-4543 to the following vulnerability:

Heap-based buffer overflow in the readchanneldata function in file-psp.c in the Paint Shop Pro (PSP) plugin in GIMP 2.6.11 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a PSPCOMPRLE (aka RLE compression) image file that begins a long run count at the end of the image. NOTE: some of these details are obtained from third party information.

Upstream bug report: [1] https://bugzilla.gnome.org/showbug.cgi?id=639203

Original patch proposal from Vincent Untz: [2] https://bugzilla.gnome.org/showbug.cgi?id=639203#c12

And final patch applied by Gimp upstream was: [3] http://git.gnome.org/browse/gimp/commit/?id=48ec15890e1751dede061f6d1f469b6508c13439

Later it was recognized by Nils Philippsen this patch to be incomplete due the following reasoning:

I've looked at this a bit further and found that even Vincent Untz's patch didn't take into account that the code that did runlength decoding actually advances by bytespp through the buffer into which it writes, so the runcount needs to be clamped to "(endq - q) / bytespp"() in order that subsequent loops don't advance past the end of the buffer.

(): This division is actually safe as bytespp is set by the plugin to one of several known values, therefore can't be 0.

Red Hat

Affected Software

1 affected component
GIMP=2.6.11

Event History

May 13, 2011
Data Sourced
02:01 PM
DescriptionSeverityAffected Software
Jul 27, 2011
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-1782?

CVE-2011-1782 is classified as a high severity vulnerability due to the potential for denial of service and arbitrary code execution.

2

How do I fix CVE-2011-1782?

To fix CVE-2011-1782, users should upgrade to a patched version of GIMP that addresses this vulnerability.

3

What applications are affected by CVE-2011-1782?

CVE-2011-1782 affects GIMP version 2.6.11 and may allow exploitation through the Paint Shop Pro plugin.

4

What type of vulnerability is CVE-2011-1782?

CVE-2011-1782 is a heap-based buffer overflow vulnerability.

5

What can attackers achieve by exploiting CVE-2011-1782?

By exploiting CVE-2011-1782, attackers could potentially crash the application or execute arbitrary code.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203