CWE
399
Advisory Published
Updated

CVE-2006-7244

First published: Wed Aug 31 2011(Updated: )

Memory leak in pngwutil.c in libpng 1.2.13beta1, and other versions before 1.2.15beta3, allows context-dependent attackers to cause a denial of service (memory leak or segmentation fault) via a JPEG image containing an iCCP chunk with a negative embedded profile length.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
libp2p=1.0.37
libp2p=1.2.14
libp2p=1.2.11-beta3
libp2p=1.0.6-e
libp2p=1.0.23-rc3
libp2p=1.0.41
libp2p=1.0.9-beta1
libp2p=1.0.15-rc1
libp2p=1.2.0-beta4
libp2p=1.0.10-beta1
libp2p=1.2.10-beta3
libp2p=1.0.7-beta13
libp2p=1.0.9-beta8
libp2p=1.0.46
libp2p=1.0.17-rc1
libp2p=1.0.29-rc3
libp2p=1.2.1-rc1
libp2p=1.0.27-rc5
libp2p=1.0.6-a
libp2p=1.0.6-d
libp2p=1.2.0-beta5
libp2p=1.0.7-beta15
libp2p=1.0.1
libp2p=1.0.8
libp2p=1.0.9-beta2
libp2p=1.2.1-beta2
libp2p=1.0.12-rc1
libp2p=1.0.29-rc1
libp2p=1.0.23-rc5
libp2p=1.0.31-rc01
libp2p=1.2.1-beta3
libp2p=1.0.14
libp2p=1.0.6-h
libp2p=1.0.27-rc1
libp2p=1.0.28-rc5
libp2p=1.0.17
libp2p=1.0.35
libp2p=1.2.10-beta6
libp2p=1.2.0
libp2p=1.0.52
libp2p=1.2.10-beta1
libp2p=1.0.28-rc3
libp2p=1.0.27
libp2p=1.0.11-rc1
libp2p=1.0.22
libp2p=1.0.11
libp2p=1.2.10-rc1
libp2p=1.0.20
libp2p=1.0.11-beta2
libp2p=1.0.9
libp2p=1.0.13
libp2p=1.0.44
libp2p=1.0.29-rc2
libp2p=1.0.23-rc2
libp2p=1.2.11-rc2
libp2p=1.0.6
libp2p=1.0.28-rc2
libp2p=1.0.7-rc1
libp2p=1.0.32
libp2p=1.2.0-rc1
libp2p=1.0.50
libp2p=1.0.7-beta12
libp2p=1.2.13-rc1
libp2p=1.0.34
libp2p=1.0.6-g
libp2p=1.0.25
libp2p=1.0.25-rc1
libp2p=1.2.13-beta1
libp2p=1.0.21
libp2p=1.0.7-beta16
libp2p=1.2.10
libp2p=1.0.43
libp2p=1.0.38
libp2p=1.0.3
libp2p=1.2.11-rc1
libp2p=1.0.40
libp2p=1.0.11-beta1
libp2p=1.0.51
libp2p=1.0.24-rc1
libp2p=1.0.11-beta3
libp2p=1.0.18
libp2p=1.0.9-rc1
libp2p=1.0.8-beta2
libp2p=1.2.15-beta1
libp2p=1.0.19-rc5
libp2p=1.2.11-beta2
libp2p=1.0.9-beta9
libp2p=1.0.54
libp2p=1.0.8-beta4
libp2p=1.0.28-rc4
libp2p=1.0.19-rc2
libp2p=1.0.19-rc3
libp2p=1.0.7
libp2p=1.0.16
libp2p=1.2.14-beta2
libp2p=1.0.9-beta6
libp2p=1.0.2
libp2p=1.0.21-rc1
libp2p=1.2.11-rc5
libp2p=1.0.10-rc1
libp2p=1.2.1-rc2
libp2p=1.2.15
libp2p=1.0.5
libp2p=1.0.9-beta3
libp2p=1.2.1
libp2p=1.2.13
libp2p=1.0.6-f
libp2p=1.0.8-rc1
libp2p=1.2.1-beta4
libp2p<=1.2.15
libp2p=1.0.29
libp2p=1.2.14-beta1
libp2p=1.0.27-rc4
libp2p=1.0.39
libp2p=1.0.27-rc6
libp2p=1.0.42
libp2p=1.0.25-rc2
libp2p=1.2.10-beta4
libp2p=1.2.0-beta1
libp2p=1.0.7-beta11
libp2p=1.0.6-i
libp2p=1.0.6-j
libp2p=1.0.24
libp2p=1.0.12
libp2p=1.2.11-beta4
libp2p=1.2.10-beta2
libp2p=1.0.15
libp2p=1.2.11
libp2p=1.2.13-rc2
libp2p=1.2.14-rc1
libp2p=1.0.15-rc2
libp2p=1.0.23-rc4
libp2p=1.0.15-rc3
libp2p=1.0.19
libp2p=1.0.9-beta4
libp2p=1.0.7-beta18
libp2p=1.0.7-beta14
libp2p=1.0.29-beta1
libp2p=1.2.0-beta3
libp2p=1.0.28
libp2p=1.0.21-rc2
libp2p=1.0.47
libp2p=1.0.8-beta1
libp2p=1.0.48
libp2p=1.0.8-beta3
libp2p=1.0.9-beta7
libp2p=1.0.7-rc2
libp2p=1.0.45
libp2p=1.0.28-rc6
libp2p=1.0.26
libp2p=1.0.9-rc2
libp2p=1.0.22-rc1
libp2p=1.0.9-beta10
libp2p=1.0.27-rc2
libp2p=1.2.11-rc3
libp2p=1.2.10-beta7
libp2p=1.2.10-rc3
libp2p=1.0.33
libp2p=1.0.23-rc1
libp2p=1.0.0
libp2p=1.2.1-beta1
libp2p=1.0.30-rc1
libp2p=1.0.53
libp2p=1.0.9-beta5
libp2p=1.2.10-rc2
libp2p=1.0.23
libp2p=1.0.30
libp2p=1.0.10
libp2p=1.0.31
libp2p=1.0.7-beta17
libp2p=1.0.19-rc1
libp2p=1.2.10-beta5
libp2p=1.2.0-beta2
libp2p=1.0.27-rc3
libp2p=1.0.12-beta1
libp2p=1.2.11-beta1

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-2006-7244?

    CVE-2006-7244 has a severity level that can lead to denial of service through a memory leak or segmentation fault.

  • How do I fix CVE-2006-7244?

    To fix CVE-2006-7244, upgrade to libpng version 1.2.15beta3 or later.

  • Which versions of libpng are affected by CVE-2006-7244?

    CVE-2006-7244 affects libpng versions 1.2.13beta1 and earlier, along with multiple earlier versions.

  • What types of attacks can exploit CVE-2006-7244?

    CVE-2006-7244 can be exploited by attackers through specially crafted JPEG images containing a malicious iCCP chunk.

  • What are the consequences of CVE-2006-7244?

    The consequences of CVE-2006-7244 include possible denial of service due to memory leaks, leading to application crashes.

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