No exploitation reportedFix available

CVE-2016-2180

No exploitation reported by the sources we read.

Published2016-08-01
WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The TS_OBJ_print_bio function in crypto/ts/ts_lib.c in the X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) implementation in OpenSSL through 1.0.2h allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted time-stamp file that is mishandled by the "openssl ts" command.

Timeline

dates in UTC

2016-08-0102:59CVE publishedNVD
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-2180?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-2180?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

OpenSSL

Branch	Affected	Fixed in	Source
1.0	= 1.0.1	no fix published	NVD
1.0	= 1.0.1a	no fix published	NVD
1.0	= 1.0.1b	no fix published	NVD
1.0	= 1.0.1c	no fix published	NVD
1.0	= 1.0.1d	no fix published	NVD
1.0	= 1.0.1e	no fix published	NVD
1.0	= 1.0.1f	no fix published	NVD
1.0	= 1.0.1g	no fix published	NVD
1.0	= 1.0.1h	no fix published	NVD
1.0	= 1.0.1i	no fix published	NVD
1.0	= 1.0.1j	no fix published	NVD
1.0	= 1.0.1k	no fix published	NVD

Oracle linux

Branch	Affected	Fixed in	Source
6.x	= 6	no fix published	NVD
7.x	= 7	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

RHSA-2016:1940 Red Hat Product Security151 products fixed
Red Hat Security Advisory: openssl security update

Full record on NVD

Fix

Vendor fix Red Hat Product Security RHSA-2016:1940 · 151 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

Advisories and patches

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.07.5read 2026-10-23
NVDCVSS 2.05read 2026-10-23
NVDweakness (CWE)CWE-125read 2026-10-23
FIRST EPSSEPSS score30.0 %read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2016-08-01
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2016-2180?

Is CVE-2016-2180 actively exploited?

Active exploitation of CVE-2016-2180 has not been confirmed. Its EPSS score was 30.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-2180?

CVE-2016-2180 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database