Loading story…
OpenSSL released fixes for seven vulnerabilities affecting older 1.0.1 and 1.0.2 branches, including high-severity CVE-2016-2108, an ASN.1 parsing and encoding flaw that can cause an out-of-bounds write and potentially exploitable memory corruption when untrusted ASN.1 data with ANY fields is reserialized. The release also fixed CVE-2016-2107, which permits a man-in-the-middle TLS/DTLS AES-CBC padding-oracle attack on AES-NI-capable servers, alongside denial-of-service, excessive-allocation, and EBCDIC overread issues.
The update additionally remediates heap-corruption defects CVE-2016-2105 and CVE-2016-2106 in the EVP_EncodeUpdate() and EVP_EncryptUpdate() APIs, respectively. Applications that directly submit exceptionally large input to these APIs may be vulnerable, while OpenSSL’s bounded internal PEM uses were not affected. OpenSSL issued versions 1.0.2h and 1.0.1t for most fixes, and Red Hat shipped patched RHEL 6 and RHEL 6.7 EUS packages; affected organizations should update and restart OpenSSL-linked services or reboot systems.
See affected versions and whether adversaries are exploiting it.
18 events from the most recent confirmed update back to the earliest known activity.
Red Hat issued Important advisory RHSA-2016:2073 for RHEL 6.7 Extended Update Support, distributing openssl-1.0.1e-42.el6_7.5. The update addressed CVE-2016-2105 through CVE-2016-2109 and other OpenSSL flaws, with service restarts or reboot required after installation.
Red Hat issued Important advisory RHSA-2016:0996 for RHEL 6, providing OpenSSL 1.0.1e-48.el6_8.1. The update remediated CVE-2016-2105 through CVE-2016-2109 among seven addressed vulnerabilities and required restarting linked services or rebooting.
Red Hat issued Important advisory RHSA-2016:0722 for RHEL 7, providing OpenSSL 1.0.1e-51.el7_2.5 to address seven vulnerabilities, including CVE-2016-2105 through CVE-2016-2109. Red Hat advised restarting OpenSSL-linked services or rebooting after installation.
OpenSSL published an advisory covering CVE-2016-2105, CVE-2016-2106, CVE-2016-2107, CVE-2016-2108, CVE-2016-2109, and CVE-2016-2176. It directed affected users to upgrade to OpenSSL 1.0.2h or 1.0.1t for most issues, while noting CVE-2016-2108 was already fixed in 1.0.2c and 1.0.1o.
Juraj Somorovsky reported CVE-2016-2107 using TLS-Attacker. The flaw allowed a man-in-the-middle attacker to use AES-NI-capable TLS servers using AES-CBC as a padding oracle to recover plaintext.
Brian Carpenter reported CVE-2016-2109, in which malformed ASN.1 data processed through BIO decoding functions could trigger excessive memory allocation and denial of service.
Guido Vranken reported CVE-2016-2105 in EVP_EncodeUpdate and CVE-2016-2106 in EVP_EncryptUpdate to the OpenSSL Project. Both flaws could cause heap corruption when applications directly process very large attacker-controlled inputs.
OpenSSL disclosed CVE-2016-0799, an integer-overflow out-of-bounds read in BIO_*printf's fmtstr function, alongside CVE-2016-2842, an out-of-bounds-write and memory-leak flaw in doapr_outch. The issues affected OpenSSL 1.0.1 and 1.0.2 primarily on platforms where size_t exceeds int, and could be triggered by applications processing very large untrusted inputs.
The fix for the negative-zero ASN.1 defect was released; it was included in OpenSSL 1.0.2c and 1.0.1o.
OpenSSL fixed the negative-zero ASN.1 defect that later formed part of CVE-2016-2108.
CVE-2016-2842 was identified in OpenSSL BIO_*printf implementations, where doapr_outch failed to handle certain memory-allocation failures. Applications processing large amounts of untrusted input could crash, and memory corruption could potentially permit code execution under the application user's privileges.
Red Hat released RHSA-2016:2957 to fix the affected OpenSSL component for CVE-2016-2107 in Text-Only JBCS.
Red Hat issued RHSA-2016:2056 to remediate CVE-2016-2105 in the OpenSSL component of affected Red Hat JBoss Enterprise Application Platform 6.4 systems.
Red Hat issued RHSA-2016:1649 to remediate CVE-2016-2106 in affected JBoss Enterprise Web Server 2 for RHEL 6 components, including httpd, jbcs-httpd24, jbcs-httpd24-openssl, mod_cluster, mod_cluster-native, and mod_jk.
Fedora EPEL 5 shipped openssl101e-1.0.1e-8.el5 to address the OpenSSL vulnerabilities.
Fedora released openssl-1.0.1k-15.fc22 to the Fedora 22 stable repository.
Fedora released openssl-1.0.2h-1.fc24 to the Fedora 24 stable repository.
Fedora released openssl-1.0.2h-1.fc23 to the Fedora 23 stable repository, addressing CVE-2016-2105 and related OpenSSL vulnerabilities.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
23 references tracked. Mallory keeps watching after this page renders.
access.redhat.com
Open sourcerhn.redhat.com
Open sourceaccess.redhat.com
Open sourcecve.org
Open sourceopenssl.org
Open sourcebugzilla.redhat.com
Open sourcebugzilla.redhat.com
Open sourcebugzilla.redhat.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
OpenSSL released versions **1.0.1u** and **1.0.2i** to correct multiple vulnerabilities affecting earlier releases. The flaws include DTLS denial-of-service issues: `CVE-2016-2181`, which lets an attacker advance a connection’s replay-protection window with an unauthenticated future-epoch record and cause valid packets to be discarded, and `CVE-2016-2179`, which can retain unnecessary out-of-order handshake fragments and consume roughly 1.5 MB of memory per DTLS connection. `CVE-2016-6302` can also crash servers using a custom SHA-512 TLS session-ticket HMAC callback through an integer underflow and out-of-bounds read. The updates additionally address memory-safety defects in certificate and utility processing. `CVE-2016-2182` is an out-of-bounds write in `BN_bn2dec()` caused by unchecked `BN_div_word()` failures when handling oversized BIGNUM values, while `CVE-2016-2180` can cause an out-of-bounds read when the `openssl ts` utility parses crafted time-stamp data containing large OIDs. `CVE-2016-6306` involves a small out-of-bounds read in certificate-message handling when client authentication is enabled. Red Hat issued fixes for affected RHEL 6 and 7 packages, including RHSA-2016:1940, with later JBoss Core Services updates for `CVE-2016-2182`.
Aug 28, 2026
OpenSSL released updates **1.1.0d** and **1.0.2k** to address several Moderate-severity defects, including `CVE-2017-3731`, an integer-underflow out-of-bounds read that lets specially truncated TLS packets crash affected 32-bit clients or servers using vulnerable cipher suites such as RC4-MD5. The releases also addressed `CVE-2017-3730`, in which malicious DHE or ECDHE parameters can trigger a NULL-pointer dereference in clients, and `CVE-2017-3732`, a carry-propagation flaw in x86_64 Montgomery squaring that can yield incorrect cryptographic results. Exploiting the latter against RSA or DSA is considered highly impractical; a Diffie-Hellman attack is more feasible only under restrictive conditions involving unpatched systems, persistent shared DH parameters, and substantial resources. Red Hat shipped updated OpenSSL packages for RHEL 6 and 7 through **RHSA-2017:0286**, remediating `CVE-2017-3731` and `CVE-2016-8610`. The latter allows unauthenticated attackers to send large volumes of malformed plaintext TLS/SSL ALERT messages during handshakes, consuming server CPU and preventing new connections; Nginx deployments were identified as affected, while Apache HTTP Server was not. Organizations should apply the vendor updates, restart all services linked to OpenSSL or reboot hosts, disable RC4-MD5 where updates cannot be immediately deployed, and retire unsupported OpenSSL 1.0.1, 1.0.0, and 0.9.8 installations.
Aug 29, 2026
OpenSSL remediated three vulnerabilities: **CVE-2019-1547**, an ECDSA timing side channel that could expose private keys when applications use explicit EC parameters without a cofactor; **CVE-2019-1549**, in which OpenSSL 1.1.1–1.1.1c may allow parent and child processes to share RNG state after `fork()`; and **CVE-2019-1563**, a Bleichenbacher-style RSA padding oracle in CMS/PKCS#7 decryption. Exploiting the ECDSA and CMS issues requires many observed signature timings or chosen-ciphertext decryption attempts, respectively; normal TLS use through `libssl` is not affected by CVE-2019-1547. Upstream fixes are available in OpenSSL 1.1.1d, 1.1.0l, and 1.0.2t, with CVE-2019-1549 fixed in 1.1.1d. Red Hat shipped backported fixes for affected JBoss Core Services Apache HTTP Server packages and RHEL 8 OpenSSL packages, advising customers to restart OpenSSL-linked services or reboot after installation. Slackware also released updated OpenSSL packages for 14.2 and -current. Organizations should patch supported OpenSSL deployments and prioritize review of applications that use explicit EC parameters, CMS/PKCS#7 RSA decryption, or forked processes relying on cryptographic randomness.
Aug 28, 2026