CVE-2016-6308: statem/statem_dtls.c in the DTLS implementation in OpenSSL 1.1.0 before 1.1.0a allocates memory before checking for an excessive length…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 12.2% (FIRST EPSS); higher than 96.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
statem/statem_dtls.c in the DTLS implementation in OpenSSL 1.1.0 before 1.1.0a allocates memory before checking for an excessive length, which might allow remote attackers to cause a denial of service (memory consumption) via crafted DTLS messages.
- Published
- Sep 26, 2016
- Updated
- Jun 16, 2026
- EPSS
- 12.2% · 96th percentile
- CWE
- CWE-399
Report tools
Action score
27
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 12.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl1.1.0
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2016-6306Sep 26, 2016 · The certificate parser in OpenSSL before 1.0.1u and 1.0.2 before 1.0.2i might allow remote attackers to cause a denial of service…36Monitor
- ← EarlierCVE-2016-6307Sep 26, 2016 · The state-machine implementation in OpenSSL 1.1.0 before 1.1.0a allocates memory before checking for an excessive length, which might allow…27Monitor
- Later →CVE-2016-6309Sep 26, 2016 · statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a…60This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (15 more)Show less
- bto.bluecoat.com/security-advisory/sa132
- cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf
- kb.juniper.net/InfoCenter/index?page=content&id=JSA10759
- www-01.ibm.com/support/docview.wss?uid=swg21995039
- www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
- www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
- www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
- www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
- www.securityfocus.com/bid/93151
- git.openssl.org/?p=openssl.git%3Ba=commit%3Bh=df6b5e29ffea2d5a3e08de92fb765fdb21c7a21e
- www.openssl.org/news/secadv/20160922.txt
- www.tenable.com/security/tns-2016-16
- www.tenable.com/security/tns-2016-20
- www.tenable.com/security/tns-2016-21
Vendor advisories and official records. Exploit/PoC links are deliberately left out.