The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169.
Category
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
5.9
CVSS
Severity: Medium
CVSS 3.1 •
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0 •
AV:N/AC:H/Au:N/C:P/I:N/A:N
EPSS
Probability of exploitation activity in the next 30 days.
CVE-2016-2107 has been scored as a medium severity vulnerability.
How to fix CVE-2016-2107?
To fix CVE-2016-2107, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-2107 being actively exploited in the wild?
It is possible that CVE-2016-2107 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~82% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.