CWE
200 456
Advisory Published
CVE Published
Updated

CVE-2013-6629: Infoleak

First published: Tue Nov 12 2013(Updated: )

It was reported [1],[2] that libjpeg and libjpeg-turbo would use uninitialized memory when decoding images with missing SOS data for the luminance component (Y) in the presence of valid chroma data (Cr, Cb). An example proof of concept that can be viewed in a browser is also available [3]. This was reported and fixed initially in Google Chrome/Chromium; it does not appear to be fixed in upstream libjpeg or libjpeg-turbo yet. Patches to the third party source in Chromium for libjpeg [4] and libjpeg-turbo [5] however are available. [1] <a href="http://googlechromereleases.blogspot.de/2013/11/stable-channel-update.html">http://googlechromereleases.blogspot.de/2013/11/stable-channel-update.html</a> [2] <a href="http://packetstormsecurity.com/files/123989/IJG-jpeg6b-libjpeg-turbo-Uninitialized-Memory.html">http://packetstormsecurity.com/files/123989/IJG-jpeg6b-libjpeg-turbo-Uninitialized-Memory.html</a> [3] <a href="http://lcamtuf.coredump.cx/jpeg_leak/">http://lcamtuf.coredump.cx/jpeg_leak/</a> [4] <a href="http://src.chromium.org/viewvc/chrome/trunk/src/third_party/libjpeg/jdmarker.c?r1=228354&amp;r2=228353&amp;pathrev=228354">http://src.chromium.org/viewvc/chrome/trunk/src/third_party/libjpeg/jdmarker.c?r1=228354&amp;r2=228353&amp;pathrev=228354</a> [5] <a href="http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/libjpeg_turbo/jdmarker.c?r1=228381&amp;r2=228380&amp;pathrev=228381">http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/libjpeg_turbo/jdmarker.c?r1=228381&amp;r2=228380&amp;pathrev=228381</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/java<1.7.0-oracle-1:1.7.0.55-1jpp.2.el5_10
1.7.0-oracle-1:1.7.0.55-1jpp.2.el5_10
redhat/java<1.6.0-sun-1:1.6.0.75-1jpp.3.el5_10
1.6.0-sun-1:1.6.0.75-1jpp.3.el5_10
redhat/java<1.7.0-oracle-1:1.7.0.55-1jpp.1.el6_5
1.7.0-oracle-1:1.7.0.55-1jpp.1.el6_5
redhat/java<1.6.0-sun-1:1.6.0.75-1jpp.1.el6_5
1.6.0-sun-1:1.6.0.75-1jpp.1.el6_5
redhat/libjpeg-turbo<0:1.2.1-3.el6_5
0:1.2.1-3.el6_5
redhat/java<1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el5
1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el5
redhat/java<1.7.0-ibm-1:1.7.0.7.0-1jpp.1.el5_10
1.7.0-ibm-1:1.7.0.7.0-1jpp.1.el5_10
redhat/java<1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el5_10
1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el5_10
redhat/java<1.5.0-ibm-1:1.5.0.16.6-1jpp.1.el5_10
1.5.0-ibm-1:1.5.0.16.6-1jpp.1.el5_10
redhat/java<1.7.0-ibm-1:1.7.0.7.0-1jpp.1.el6_5
1.7.0-ibm-1:1.7.0.7.0-1jpp.1.el6_5
redhat/java<1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el6_5
1.6.0-ibm-1:1.6.0.16.0-1jpp.1.el6_5
redhat/java<1.5.0-ibm-1:1.5.0.16.6-1jpp.1.el6_5
1.5.0-ibm-1:1.5.0.16.6-1jpp.1.el6_5
redhat/java<1.7.1-ibm-1:1.7.1.1.0-1jpp.2.el7_0
1.7.1-ibm-1:1.7.1.1.0-1jpp.2.el7_0
Google Chrome (Trace Event)<31.0.1650.48
Oracle Solaris and Zettabyte File System (ZFS)=11.3
Ghostscript<9.03
Libjpeg-turbo-devel<1.3.1
Fedora=18
Fedora=19
Fedora=20
SUSE Linux=12.2
SUSE Linux=12.3
SUSE Linux=13.1
Ubuntu=10.04
Ubuntu=12.04
Ubuntu=12.10
Ubuntu=13.04
Ubuntu=13.10
Debian=7.0
Debian=8.0
Firefox<26.0
Firefox ESR<24.2
Mozilla SeaMonkey<2.23
Thunderbird<24.2.0

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.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-6629?

    The severity of CVE-2013-6629 is rated as moderate, but it can lead to potential security issues due to uninitialized memory usage.

  • How do I fix CVE-2013-6629?

    To fix CVE-2013-6629, update the affected software to the recommended versions such as libjpeg-turbo 1.2.1-3.el6_5 or the respective patched versions for Java.

  • What software is affected by CVE-2013-6629?

    CVE-2013-6629 affects several packages, including libjpeg-turbo and various Java versions from Red Hat.

  • Can exploiting CVE-2013-6629 lead to information leakage?

    Yes, exploiting CVE-2013-6629 could potentially lead to information leakage due to the way uninitialized memory is handled.

  • Are there known exploits for CVE-2013-6629?

    While there is a proof of concept available, specific public exploits for CVE-2013-6629 have not been widely reported.

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