CVE-2016-2177: Integer Overflow
A common idiom in the codebase is:
if (p + len > limit) { return; / Too long / }
where p points to some malloc'd data of SIZE bytes and limit == p + SIZE. 'len' could be from some externally supplied data, e.g. TLS message. This idiom is vulnerable to integer overflow vulnerability.
Other sources
Multiple integer overflow flaws were found in the way OpenSSL performed pointer arithmetic. A remote attacker could possibly use these flaws to cause a TLS/SSL server or client using OpenSSL to crash.
OpenSSL through 1.0.2h incorrectly uses pointer arithmetic for heap-buffer boundary checks, which might allow remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact by leveraging unexpected malloc behavior, related to s3srvr.c, sslsess.c, and t1lib.c.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2016-2177?
CVE-2016-2177 has been assigned a medium severity rating due to its potential for integer overflow that could lead to denial of service or other vulnerabilities.
How do I fix CVE-2016-2177?
To fix CVE-2016-2177, update your affected software packages to the recommended versions as listed in the vulnerability details.
Which software versions are affected by CVE-2016-2177?
CVE-2016-2177 affects multiple versions of jbcs-httpd24-httpd, jbcs-httpd24-nghttp2, and jbcs-httpd24-openssl among others, specifically prior to their respective fixed versions.
What causes CVE-2016-2177?
CVE-2016-2177 is caused by an integer overflow vulnerability stemming from an improper check on input lengths that can lead to excessive memory access.
Is CVE-2016-2177 a widely exploited vulnerability?
While not widely exploited in the wild, CVE-2016-2177 presents a significant risk if left unpatched, especially in systems reliant on the affected software.