CVE-2016-2180

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.

We have discovered 435,656 live websites that are affected by CVE-2016-2180.

Test my site



Affected Software

Product  OpenSSL
Category Web Server Extensions
Vulnerable Domains435,656 live websites (64.98% of OpenSSL install base)
Vulnerable Versions
  • from 0 through 1.0.2
Vulnerable Versions Count11 versions ( 27.50% of all versions)



Details

  • Published - Aug 1, 2016
  • Updated - Aug 5, 2024

CVE-2016-2180 usage by Country

United States147,528 websites


Germany40,012 websites
Japan26,014 websites
Netherlands25,701 websites
Korea, South16,444 websites
Singapore14,973 websites
France14,825 websites
Russia12,153 websites
China10,289 websites

CVE-2016-2180 usage by TLD

.com158,187 websites
.de28,374 websites
.net19,614 websites
.nl18,988 websites
.org16,522 websites
.ru10,634 websites
.jp10,293 websites
.cz8,212 websites
.it7,701 websites
.com.br5,622 websites

Vulnerable Versions

Vulnerable versions are highlighted in red

Websites affected by CVE-2016-2180

Top websites that are affected by CVE-2016-2180. Please click on the "Contact us" link to get more information.
DomainCountryRankContacts
*********.*************.se United States***
****.com United States***
********.*********.com Singapore*,***
****.com United States*,***
********.com United States*,***
*******.com United States*,***
*.******.***.***.br Brazil*,***
*************.com GB*,***
*.*****.***.***.br Brazil*,***
****.**.com United States*,***
See full domain list

FAQ

A total of 435,656 websites have been identified as vulnerable to CVE-2016-2180, discovered through global website indexing conducted by WebTechSurvey.
OpenSSL is susceptible to CVE-2016-2180 vulnerability.
OpenSSL versions before, and including, 1.0.2 are vulnerable to CVE-2016-2180.

References