Loading story…
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.
See real exploitation activity before you spend the cycle.
11 events from the most recent confirmed update back to the earliest known activity.
Red Hat marked affected JBoss Core Services on RHEL 6 components as fixed by RHSA-2018:2186 for CVE-2016-6306. The OpenSSL handshake-message out-of-bounds read flaws could allow a remote unauthenticated attacker to crash a TLS/SSL client or server.
Red Hat issued RHSA-2018:2186 to fix CVE-2016-2182 in listed JBoss Core Services on RHEL 6 components, including HTTP Server-related packages. The issue was an unchecked-error out-of-bounds write in OpenSSL's BN_bn2dec() function.
Red Hat released RHSA-2016:1940 for Red Hat Enterprise Linux 6 and 7, fixing CVE-2016-2179 in OpenSSL. A malicious DTLS client could cause unreleased fragment-buffer memory to accumulate and potentially terminate a DTLS server through memory exhaustion.
Red Hat released RHSA-2016:1940 for Red Hat Enterprise Linux 6 and 7, remediating CVE-2016-2181. The vulnerability could let a remote attacker cause an established OpenSSL DTLS connection to reject subsequent client packets.
OpenSSL published its September 2016 security advisory and released 1.0.1u and 1.0.2i, fixing CVE-2016-2179, CVE-2016-2180, CVE-2016-2181, CVE-2016-2182, CVE-2016-6302, and CVE-2016-6306. Users of the affected 1.0.1 and 1.0.2 branches were advised to upgrade.
Shi Lei of Qihoo 360's Gear Team reported CVE-2016-6306 to OpenSSL. Missing certificate-message length checks could cause an out-of-bounds read of up to two bytes when client authentication was enabled.
Shi Lei of Qihoo 360's Gear Team reported CVE-2016-6302 to OpenSSL. A malformed session ticket using a SHA-512 HMAC in a custom ticket configuration could underflow a length value and crash a TLS server.
Shi Lei of Qihoo 360's Gear Team reported CVE-2016-2182 to OpenSSL. Unchecked BN_div_word() failures in BN_bn2dec() could lead to out-of-bounds writes when processing an oversized BIGNUM.
Shi Lei of Qihoo 360's Gear Team reported CVE-2016-2180 to OpenSSL. Large object identifiers processed by the Time-Stamp Protocol code could cause an out-of-bounds read and crash the openssl ts utility.
Quan Luo reported CVE-2016-2179 to OpenSSL. The DTLS handshake logic could retain unneeded out-of-order messages after a handshake, allowing memory exhaustion across many connections.
The OCAP audit team reported CVE-2016-2181 to OpenSSL. The flaw allowed a future-epoch DTLS record with a large sequence number to advance the replay window before MAC validation, enabling denial of service for a connection.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
18 references tracked. Mallory keeps watching after this page renders.
cve.org
Open sourcecve.org
Open sourcecve.org
Open sourcecve.org
Open sourceredhat.com
Open sourceopenssl.org
Open sourcebugzilla.redhat.com
Open sourcecwe.mitre.org
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 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 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.
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