Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2016-2177

Integer Overflow or Wraparound

Published: Jun 20, 2016 | Modified: Nov 07, 2023
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
2.6 LOW
AV:N/AC:H/Au:N/C:N/I:N/A:P
RedHat/V3
5.9 LOW
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
LOW
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2016-2177
CWEhttps://cwe.mitre.org/data/definitions/190.html

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 s3_srvr.c, ssl_sess.c, and t1_lib.c.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.

Affected Software

Name Vendor Start Version End Version
Icewall_mcrp Hp 3.0 (including) 3.0 (including)
Icewall_sso Hp 10.0 (including) 10.0 (including)
Icewall_sso_agent_option Hp 10.0 (including) 10.0 (including)
Openssl Ubuntu artful *
Openssl Ubuntu bionic *
Openssl Ubuntu cosmic *
Openssl Ubuntu devel *
Openssl Ubuntu disco *
Openssl Ubuntu precise *
Openssl Ubuntu trusty *
Openssl Ubuntu upstream *
Openssl Ubuntu vivid/stable-phone-overlay *
Openssl Ubuntu vivid/ubuntu-core *
Openssl Ubuntu wily *
Openssl Ubuntu xenial *
Openssl Ubuntu yakkety *
Openssl Ubuntu zesty *
Openssl098 Ubuntu precise *
Openssl098 Ubuntu trusty *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-httpd-0:2.4.23-102.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_auth_kerb-0:5.4-35.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_bmx-0:0.9.6-14.GA.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_cluster-native-0:1.3.5-13.Final_redhat_1.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_jk-0:1.2.41-14.redhat_1.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_rt-0:2.4.1-16.GA.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_security-0:2.9.1-18.GA.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-nghttp2-0:1.12.0-9.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-openssl-1:1.0.2h-12.jbcs.el6 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-httpd-0:2.4.23-102.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_auth_kerb-0:5.4-35.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_bmx-0:0.9.6-14.GA.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_cluster-native-0:1.3.5-13.Final_redhat_1.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_jk-0:1.2.41-14.redhat_1.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_rt-0:2.4.1-16.GA.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_security-0:2.9.1-18.GA.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-nghttp2-0:1.12.0-9.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-openssl-1:1.0.2h-12.jbcs.el7 *
Red Hat Enterprise Linux 6 RedHat openssl-0:1.0.1e-48.el6_8.3 *
Red Hat Enterprise Linux 7 RedHat openssl-1:1.0.1e-51.el7_2.7 *
Red Hat JBoss Core Services 1 RedHat *
Red Hat JBoss Enterprise Application Platform 6.4 RedHat openssl *
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 RedHat jbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el6 *
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7 RedHat jbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el7 *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use