CWE
399 119
Advisory Published
CVE Published
Updated

CVE-2008-1097: Buffer Overflow

First published: Tue Sep 11 2007(Updated: )

Description of the probem: Attemting to display a broken PCX file results in a heap corruption: Steps to reproduce: (gdb) run broken.pcx [Thread debugging using libthread_db enabled] [New Thread -1208564032 (LWP 31972)] *** glibc detected *** /usr/bin/display: malloc(): memory corruption: 0x087e42c0 *** ... Program received signal SIGABRT, Aborted. [Switching to Thread -1208564032 (LWP 31972)] 0x00110402 in __kernel_vsyscall () (gdb) Version-Release number of selected component (if applicable): ImageMagick-6.2.8.0-3.el5.4 Additional information: Debian bug referenced in URL might contain more informaion.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
ImageMagick=1.1.9
ImageMagick=1.1.7
ImageMagick=1.1.10
ImageMagick=1.1.11
ImageMagick=6.2.8.1
ImageMagick=6.2.8.0
ImageMagick=1.1.8
ImageMagick=1.1.12
ImageMagick=6.2.8.3
ImageMagick=6.2.8.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2008-1097?

    CVE-2008-1097 is considered a moderate severity vulnerability due to potential heap corruption leading to application crashes.

  • How do I fix CVE-2008-1097?

    To fix CVE-2008-1097, upgrade to a patched version of ImageMagick or GraphicsMagick that addresses the heap corruption issue.

  • What software versions are affected by CVE-2008-1097?

    CVE-2008-1097 affects multiple versions of ImageMagick and GraphicsMagick, including versions 1.1.7 through 1.1.12 and 6.2.8.0 through 6.2.8.3.

  • Can CVE-2008-1097 lead to arbitrary code execution?

    While CVE-2008-1097 primarily results in a crash due to heap corruption, it could potentially be exploited to execute arbitrary code under specific conditions.

  • What types of files can trigger CVE-2008-1097?

    CVE-2008-1097 can be triggered by attempting to display a broken PCX file, leading to memory corruption.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203