CVE-2016-2179

What it is

The DTLS implementation in OpenSSL before 1.1.0 does not properly restrict the lifetime of queue entries associated with unused out-of-order messages, which allows remote attackers to cause a denial of service (memory consumption) by maintaining many crafted DTLS sessions simultaneously, related to d1_lib.c, statem_dtls.c, statem_lib.c, and statem_srvr.c.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

26.6% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2016-09-16 05:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 26.6% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2016-09-16 05:59 UTC

Last modified

2026-06-17 00:43 UTC

Exploit probability

26.6% · EPSS, next 30 days

Weakness

CWE-399

Record status

Modified

Affected

• OpenSSL 1.0.1
• OpenSSL 1.0.1a
• OpenSSL 1.0.1b
• OpenSSL 1.0.1c
• OpenSSL 1.0.1d
• OpenSSL 1.0.1e
• OpenSSL 1.0.1f
• OpenSSL 1.0.1g

Attack profile CVSS 3.0 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-2179.md and follow it. Check whether this project is affected by CVE-2016-2179. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge