Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2016-2178

Observable Discrepancy

Published: Jun 20, 2016 | Modified: Nov 07, 2023
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
1.9 MODERATE
AV:L/AC:M/Au:N/C:P/I:N/A:N
RedHat/V3
5.1 MODERATE
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
LOW
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2016-2178
CWEhttps://cwe.mitre.org/data/definitions/203.html

The dsa_sign_setup function in crypto/dsa/dsa_ossl.c in OpenSSL through 1.0.2h does not properly ensure the use of constant-time operations, which makes it easier for local users to discover a DSA private key via a timing side-channel attack.

Weakness

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

Affected Software

Name Vendor Start Version End Version
Openssl Openssl 1.0.1 (including) 1.0.1 (including)
Openssl Openssl 1.0.1a (including) 1.0.1a (including)
Openssl Openssl 1.0.1b (including) 1.0.1b (including)
Openssl Openssl 1.0.1c (including) 1.0.1c (including)
Openssl Openssl 1.0.1d (including) 1.0.1d (including)
Openssl Openssl 1.0.1e (including) 1.0.1e (including)
Openssl Openssl 1.0.1f (including) 1.0.1f (including)
Openssl Openssl 1.0.1g (including) 1.0.1g (including)
Openssl Openssl 1.0.1h (including) 1.0.1h (including)
Openssl Openssl 1.0.1i (including) 1.0.1i (including)
Openssl Openssl 1.0.1j (including) 1.0.1j (including)
Openssl Openssl 1.0.1k (including) 1.0.1k (including)
Openssl Openssl 1.0.1l (including) 1.0.1l (including)
Openssl Openssl 1.0.1m (including) 1.0.1m (including)
Openssl Openssl 1.0.1n (including) 1.0.1n (including)
Openssl Openssl 1.0.1o (including) 1.0.1o (including)
Openssl Openssl 1.0.1p (including) 1.0.1p (including)
Openssl Openssl 1.0.1q (including) 1.0.1q (including)
Openssl Openssl 1.0.1r (including) 1.0.1r (including)
Openssl Openssl 1.0.1s (including) 1.0.1s (including)
Openssl Openssl 1.0.1t (including) 1.0.1t (including)
Openssl Openssl 1.0.2 (including) 1.0.2 (including)
Openssl Openssl 1.0.2a (including) 1.0.2a (including)
Openssl Openssl 1.0.2b (including) 1.0.2b (including)
Openssl Openssl 1.0.2c (including) 1.0.2c (including)
Openssl Openssl 1.0.2d (including) 1.0.2d (including)
Openssl Openssl 1.0.2e (including) 1.0.2e (including)
Openssl Openssl 1.0.2f (including) 1.0.2f (including)
Openssl Openssl 1.0.2g (including) 1.0.2g (including)
Openssl Openssl 1.0.2h (including) 1.0.2h (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

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

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