CVE-2016-0736

UnknownEPSS 49.02%

Last modified

CVE-2016-0736 is a vulnerability of currently unknown severity. In Apache HTTP Server versions 2.4.0 to 2.4.23, mod_session_crypto was encrypting its data/cookie using the configured ciphers with possibly either CBC or ECB modes of operation (AES256-CBC by default), hence no selectable or builtin authenticated encryption. This made it vulnerable to padding oracle attacks, particularly with CBC.. EPSS estimates a 49.02% chance of exploitation in the next 30 days.

Description

In Apache HTTP Server versions 2.4.0 to 2.4.23, mod_session_crypto was encrypting its data/cookie using the configured ciphers with possibly either CBC or ECB modes of operation (AES256-CBC by default), hence no selectable or builtin authenticated encryption. This made it vulnerable to padding oracle attacks, particularly with CBC.

Metrics

EPSS Probability
49.02%

98.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ApacheHttp Server2.4.0
ApacheHttp Server2.4.1
ApacheHttp Server2.4.2
ApacheHttp Server2.4.3
ApacheHttp Server2.4.6
ApacheHttp Server2.4.7
ApacheHttp Server2.4.8
ApacheHttp Server2.4.9
ApacheHttp Server2.4.10
ApacheHttp Server2.4.12
ApacheHttp Server2.4.14
ApacheHttp Server2.4.16
ApacheHttp Server2.4.19
ApacheHttp Server2.4.20
ApacheHttp Server2.4.21
ApacheHttp Server2.4.22
ApacheHttp Server2.4.23

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-0736?
In Apache HTTP Server versions 2.4.0 to 2.4.23, mod_session_crypto was encrypting its data/cookie using the configured ciphers with possibly either CBC or ECB modes of operation (AES256-CBC by default), hence no selectable or builtin authenticated encryption. This made it vulnerable to padding oracle attacks, particularly with CBC.
How severe is CVE-2016-0736?
Severity scoring for CVE-2016-0736 is pending analysis. The EPSS model estimates a 49.02% probability of exploitation in the next 30 days.
How do I fix CVE-2016-0736?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-0736?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST