high
7.5
CWE
399 772
Advisory Published
CVE Published
Updated

CVE-2016-2179

First published: Thu Jun 30 2016(Updated: )

It was discovered that the Datagram TLS (DTLS) implementation could fail to release memory in certain cases. A malicious DTLS client could cause a DTLS server using OpenSSL to consume an excessive amount of memory and, possibly, exit unexpectedly after exhausting all available memory.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/openssl<0:1.0.1e-48.el6_8.3
0:1.0.1e-48.el6_8.3
redhat/openssl<1:1.0.1e-51.el7_2.7
1:1.0.1e-51.el7_2.7
redhat/openssl<1.0.1
1.0.1
redhat/openssl<1.0.2
1.0.2
OpenSSL libcrypto=1.0.1
OpenSSL libcrypto=1.0.1a
OpenSSL libcrypto=1.0.1b
OpenSSL libcrypto=1.0.1c
OpenSSL libcrypto=1.0.1d
OpenSSL libcrypto=1.0.1e
OpenSSL libcrypto=1.0.1f
OpenSSL libcrypto=1.0.1g
OpenSSL libcrypto=1.0.1h
OpenSSL libcrypto=1.0.1i
OpenSSL libcrypto=1.0.1j
OpenSSL libcrypto=1.0.1k
OpenSSL libcrypto=1.0.1l
OpenSSL libcrypto=1.0.1m
OpenSSL libcrypto=1.0.1n
OpenSSL libcrypto=1.0.1o
OpenSSL libcrypto=1.0.1p
OpenSSL libcrypto=1.0.1q
OpenSSL libcrypto=1.0.1r
OpenSSL libcrypto=1.0.1s
OpenSSL libcrypto=1.0.1t
OpenSSL libcrypto=1.0.2
OpenSSL libcrypto=1.0.2a
OpenSSL libcrypto=1.0.2b
OpenSSL libcrypto=1.0.2c
OpenSSL libcrypto=1.0.2d
OpenSSL libcrypto=1.0.2e
OpenSSL libcrypto=1.0.2f
OpenSSL libcrypto=1.0.2g
OpenSSL libcrypto=1.0.2h
Oracle Linux=6
Oracle Linux=7
debian/openssl
1.1.1w-0+deb11u1
1.1.1w-0+deb11u2
3.0.15-1~deb12u1
3.0.14-1~deb12u2
3.4.0-2
3.4.1-1

Remedy

https://git.openssl.org/?p=openssl.git;a=commit;h=f5c7f5dfbaf0d2f7d946d0fe86f08e6bcb36ed0d

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

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2016-2179?

    CVE-2016-2179 is rated as moderate severity due to its impact on memory consumption.

  • How do I fix CVE-2016-2179?

    To fix CVE-2016-2179, upgrade to the latest versions of OpenSSL specified in vendor advisories that patch the vulnerability.

  • What impact does CVE-2016-2179 have on affected systems?

    CVE-2016-2179 can lead to excessive memory consumption by a malicious DTLS client, potentially causing the server to become unresponsive.

  • Which versions of OpenSSL are affected by CVE-2016-2179?

    OpenSSL versions 1.0.1e and earlier, as well as other specified versions, are vulnerable to CVE-2016-2179.

  • Is there a workaround for CVE-2016-2179 until a patch is applied?

    Currently, the best workaround for CVE-2016-2179 is to restrict untrusted DTLS clients or protocols until a patch can be implemented.

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