Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2016-2105

Integer Overflow or Wraparound

Published: May 05, 2016 | Modified: Apr 12, 2025
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
5.1 MODERATE
AV:N/AC:H/Au:N/C:P/I:P/A:P
RedHat/V3
5.6 MODERATE
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Ubuntu
LOW
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2016-2105
CWEhttps://cwe.mitre.org/data/definitions/190.html

Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (heap memory corruption) via a large amount of binary data.

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 occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Affected Software

Name Vendor Start Version End Version
Enterprise_linux_desktop Redhat 6.0 (including) 6.0 (including)
Enterprise_linux_hpc_node Redhat 6 (including) 6 (including)
Enterprise_linux_server Redhat 6.0 (including) 6.0 (including)
Enterprise_linux_workstation Redhat 6.0 (including) 6.0 (including)
Red Hat Enterprise Linux 6 RedHat openssl-0:1.0.1e-48.el6_8.1 *
Red Hat Enterprise Linux 6.7 Extended Update Support RedHat openssl-0:1.0.1e-42.el6_7.5 *
Red Hat Enterprise Linux 7 RedHat openssl-1:1.0.1e-51.el7_2.5 *
Red Hat JBoss Enterprise Application Platform 6.4 RedHat openssl *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat httpd-0:2.2.26-54.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat jbcs-httpd24-0:1-3.jbcs.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat jbcs-httpd24-openssl-1:1.0.2h-4.jbcs.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat mod_cluster-0:1.2.13-1.Final_redhat_1.1.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat mod_cluster-native-0:1.2.13-3.Final_redhat_2.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat mod_jk-0:1.2.41-2.redhat_3.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat tomcat-native-0:1.1.34-5.redhat_1.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat httpd22-0:2.2.26-56.ep6.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat jbcs-httpd24-0:1-3.jbcs.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat jbcs-httpd24-openssl-1:1.0.2h-4.jbcs.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat mod_cluster-0:1.2.13-1.Final_redhat_1.1.ep6.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat mod_cluster-native-0:1.2.13-3.Final_redhat_2.ep6.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat mod_jk-0:1.2.41-2.redhat_3.ep6.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat tomcat-native-0:1.1.34-5.redhat_1.ep6.el7 *
Red Hat JBoss Web Server 2.1 RedHat openssl *
Text-Only JBCS RedHat *
Openssl Ubuntu artful *
Openssl Ubuntu bionic *
Openssl Ubuntu cosmic *
Openssl Ubuntu devel *
Openssl Ubuntu disco *
Openssl Ubuntu esm-infra-legacy/trusty *
Openssl Ubuntu esm-infra/bionic *
Openssl Ubuntu esm-infra/xenial *
Openssl Ubuntu precise *
Openssl Ubuntu trusty *
Openssl Ubuntu trusty/esm *
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 *

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 [REF-1482].
  • 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 © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use