medium
4.3
CWE
310
Advisory Published
CVE Published
Updated

CVE-2013-6449

First published: Fri Dec 20 2013(Updated: )

A flaw was reported for OpenSSL 1.0.1e, that can cause application using OpenSSL to crash when using TLS version 1.2. Issue was reported via the following OpenSSL upstream ticket: <a href="http://rt.openssl.org/Ticket/Display.html?id=3200&amp;user=guest&amp;pass=guest">http://rt.openssl.org/Ticket/Display.html?id=3200&amp;user=guest&amp;pass=guest</a> and also as bug for Apache Traffic Server: <a href="https://issues.apache.org/jira/browse/TS-2355">https://issues.apache.org/jira/browse/TS-2355</a> Fix is now committed in upstream git: <a href="http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ca98926">http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ca98926</a> Related to the above ticket, upstream also added this fix to improve error checks in OpenSSL: <a href="http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0294b2b">http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0294b2b</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/openssl<1.0.1
1.0.1
OpenSSL<=1.0.1e
OpenSSL=1.0.0
OpenSSL=1.0.0-beta1
OpenSSL=1.0.0-beta2
OpenSSL=1.0.0-beta3
OpenSSL=1.0.0-beta4
OpenSSL=1.0.0-beta5
OpenSSL=1.0.0a
OpenSSL=1.0.0b
OpenSSL=1.0.0c
OpenSSL=1.0.0d
OpenSSL=1.0.0e
OpenSSL=1.0.0f
OpenSSL=1.0.0g
OpenSSL=1.0.0h
OpenSSL=1.0.0i
OpenSSL=1.0.0j
OpenSSL=1.0.1
OpenSSL=1.0.1-beta1
OpenSSL=1.0.1-beta2
OpenSSL=1.0.1-beta3
OpenSSL=1.0.1a
OpenSSL=1.0.1b
OpenSSL=1.0.1c
OpenSSL=1.0.1d

Remedy

http://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=ca989269a2876bae79393bd54c3e72d49975fc75

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2013-6449 has a moderate severity level as it can cause application crashes when using affected OpenSSL versions.

  • How do I fix CVE-2013-6449?

    To fix CVE-2013-6449, upgrade OpenSSL to version 1.0.1g or higher.

  • Which versions of OpenSSL are affected by CVE-2013-6449?

    CVE-2013-6449 affects OpenSSL versions up to and including 1.0.1e.

  • What are the symptoms of CVE-2013-6449?

    The main symptom of CVE-2013-6449 is that applications using OpenSSL may crash when utilizing TLS version 1.2.

  • Is CVE-2013-6449 exploitable remotely?

    CVE-2013-6449 is not directly exploitable for remote attacks, but it can lead to denial of service through application crashes.

Company

Resources

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