medium
4.3
CWE
310
Advisory Published
Updated

CVE-2011-4108

First published: Fri Jan 06 2012(Updated: )

The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
OpenSSL libcrypto=0.9.8b
OpenSSL libcrypto=0.9.7l
OpenSSL libcrypto=0.9.6i
OpenSSL libcrypto=0.9.8m
OpenSSL libcrypto=0.9.8c
OpenSSL libcrypto=0.9.7c
OpenSSL libcrypto=0.9.8n
OpenSSL libcrypto=0.9.8p
OpenSSL libcrypto=0.9.6d
OpenSSL libcrypto=0.9.1c
OpenSSL libcrypto=0.9.6
OpenSSL libcrypto=0.9.7j
OpenSSL libcrypto=0.9.6a
OpenSSL libcrypto=0.9.8e
OpenSSL libcrypto=0.9.6h-bogus
OpenSSL libcrypto=0.9.4
OpenSSL libcrypto=0.9.8g
OpenSSL libcrypto=0.9.8k
OpenSSL libcrypto=0.9.8d
OpenSSL libcrypto=0.9.5a
OpenSSL libcrypto=0.9.6f
OpenSSL libcrypto=0.9.8j
OpenSSL libcrypto=0.9.6l
OpenSSL libcrypto=0.9.7k
OpenSSL libcrypto=0.9.7g
OpenSSL libcrypto<=0.9.8r
OpenSSL libcrypto=0.9.6e
OpenSSL libcrypto=0.9.7d
OpenSSL libcrypto=0.9.8l
OpenSSL libcrypto=0.9.7
OpenSSL libcrypto=0.9.6b
OpenSSL libcrypto=0.9.7e
OpenSSL libcrypto=0.9.7b
OpenSSL libcrypto=0.9.6k
OpenSSL libcrypto=0.9.8a
OpenSSL libcrypto=0.9.6g
OpenSSL libcrypto=0.9.7m
OpenSSL libcrypto=0.9.6h
OpenSSL libcrypto=0.9.7i
OpenSSL libcrypto=0.9.7h
OpenSSL libcrypto=0.9.8o
OpenSSL libcrypto=0.9.8q
OpenSSL libcrypto=0.9.6j
OpenSSL libcrypto=0.9.8
OpenSSL libcrypto=0.9.7a
OpenSSL libcrypto=0.9.6c
OpenSSL libcrypto=0.9.6m
OpenSSL libcrypto=0.9.8i
OpenSSL libcrypto=0.9.8f
OpenSSL libcrypto=0.9.8h
OpenSSL libcrypto=0.9.2b
OpenSSL libcrypto=0.9.5
OpenSSL libcrypto=0.9.7f
OpenSSL libcrypto=1.0.0c
OpenSSL libcrypto=1.0.0-beta1
OpenSSL libcrypto=1.0.0-beta2
OpenSSL libcrypto=1.0.0-beta3
OpenSSL libcrypto=1.0.0d
OpenSSL libcrypto<=1.0.0e
OpenSSL libcrypto=1.0.0-beta4
OpenSSL libcrypto=1.0.0
OpenSSL libcrypto=1.0.0-beta5
OpenSSL libcrypto=1.0.0a
OpenSSL libcrypto=1.0.0b

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-2011-4108?

    CVE-2011-4108 is categorized as a high severity vulnerability due to its potential to allow remote attackers to recover plaintext data.

  • How do I fix CVE-2011-4108?

    To mitigate CVE-2011-4108, update OpenSSL to versions 0.9.8s or 1.0.0f or later, which contain the security fix.

  • What systems are affected by CVE-2011-4108?

    CVE-2011-4108 affects various OpenSSL versions including 0.9.8b through 0.9.8r and 1.0.0beta1 through 1.0.0e.

  • How does CVE-2011-4108 work?

    CVE-2011-4108 exploits a padding oracle attack that can bypass MAC checks, enabling plaintext recovery.

  • Is CVE-2011-4108 still relevant today?

    CVE-2011-4108 remains relevant for systems still running affected OpenSSL versions, emphasizing the need for regular updates.

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