Browse Source

Add GlobalSign and StartCom incidents, and move current company operation status out of the headers

Sven Slootweg 7 years ago
  1. 30


@ -52,7 +52,9 @@ This list is sorted alphabetically by the names of the Certificate Authorities.
* __November 2011:__ Digicert Malaysia is blacklisted by Microsoft, Google and Mozilla after issuing 22 certificates with serious security deficiencies. Their intermediate CA certificate is also revoked by Entrust. ([source](
### DigiNotar (now defunct)
### DigiNotar
__Now defunct.__
* __July 10, 2011:__ DigiNotar issues fraudulent wildcard certificate for Google that is later used in an MITM attack. ([source](
* __August 2011:__ It becomes clear that hundreds of fraudulent certificates were created. The total count of fraudulent certificates is at least 531. ([source](
@ -62,17 +64,22 @@ This list is sorted alphabetically by the names of the Certificate Authorities.
* __November 2011:__ Entrust is involved in the Digicert Malaysia incident (see above), and has apparently failed to audit the intermediary CA. They revoke Digicert Malaysia's intermediate certificate after the incident becomes public. ([source](
### Gemnet (owned by KPN)
### Gemnet
__Owned by KPN.__
* __December 2011:__ Gemnet is compromised through an unsecured and passwordless public instance of PHPMyAdmin. It is unclear whether fraudulent certificates were issued, or whether confidential information was leaked. ([source](
### Getronics / KPN Corporate Market (owned by KPN)
### Getronics / KPN Corporate Market
__Owned by KPN.__
* __November 2011:__ Evidence surfaces that Getronics was compromised 4 years earlier, but Getronics claims that no production servers were affected. ([source](, [source](
### GlobalSign
* __September 2011:__ A webserver at GlobalSign is compromised. GlobalSign notes that there was no evidence of fraudulent certificate issuance, and that the issuance systems were airgapped and thus not affected. ([source](
* __October 13, 2016:__ GlobalSign erroneously revokes an intermediary certificate, leading to certificate validation errors for many (major and smaller) customers, on otherwise valid certificates. ([source](
### Kazakh Government
@ -88,9 +95,18 @@ This list is sorted alphabetically by the names of the Certificate Authorities.
* __July 8, 2014:__ Google announces that it has detected fraudulently certificates for various Google domains, issued by the National Informatics Centre of India. The certificates were likely used for an MITM attack. ([source](
### StartCom (now likely owned by WoSign)
### StartCom
* __April 2014:__ StartCom refuses to revoke certificates that were (potentially) compromised through HeartBleed. ([source](
__Now owned by [WoSign](#wosign), and has been quietly operating under WoSign for an unknown length of time, prior to public disclosure.__
* __December 2008:__ StartCom's founder, Eddy Nigg, obtains a fraudulent certificate from Comodo for ``. While this was allegedly for the purpose of demonstrating an issue with Comodo, Nigg subsequently uses the certificate on a public-facing web server, and threatens the release of its private key. ([source](
* __April 2014:__ StartCom refuses to revoke certificates that were (potentially) compromised through HeartBleed, thereby violating CA requirements. ([source](, [source](
* __May 2014 (and ongoing?):__ StartCom issues multiple certificates that are shorter than the required 2048 bits, thereby violating CA requirements. This is allegedly due to a software bug, but StartCom has failed to provide further details or clear remediation. ([source](
* __June 2014:__ StartCom issues at least ~30 certificates with duplicate serial numbers, and fails to timely respond to a report about this from Mozilla. ([source](
* __October 2015:__ StartCom's OCSP server experiences severe delays in confirming newly issued certificates, leading to certificate validation errors in Firefox for otherwise valid certificates. ([source](, [source](
* __October 2015:__ StartCom fails to verify that the RSA public key exponent for a certificate equals 3 or higher, thereby violating CA requirements. ([source](
* __April 2016:__ StartCom issues 7 certificates that are missing a `localityName` and `stateOrProvinceName`, thereby violating CA requirements. ([source](
* __May 2016:__ StartCom issues certificates using the disallowed secp256k1 curve, thereby violating CA requirements. ([source](
* __June 18, 2016:__ StartCom launches a service named "StartEncrypt", which is essentially a clone of Let's Encrypt - however, it requires the installation of a binary, with no ability to inspect the source code. (source: see `sources/startencrypt.txt`)
* __June 30, 2016:__ StartEncrypt is found to have numerous vulnerabilities, including multiple critical vulnerabilities that resulted in the possibility of misissuance for high-profile domains such as ``, ``, ``, ``, and ``. ([source](
* __July 2016:__ StartCom, in its StartEncrypt API, allows issuance of SHA1 certificates, in violation of CA requirements. The certificates are also backdated to December 20, 2015, and signed by WoSign rather than StartCom. The incident was not reported to Mozilla as it should have been. ([source](
@ -110,7 +126,9 @@ This list is sorted alphabetically by the names of the Certificate Authorities.
* __Late 2011:__ TÜRKTRUST hands out subordinate certificates to the Turkish government and a Turkish bank and fails to disclose the existence of these certificates, allowing these organizations to issue their own (CA-validated) certificates. One of these certificates was used to issue a certificate for ``. ([source](
### Verisign (CA is now owned by Symantec)
### Verisign
__The CA part of VeriSign is now owned by [Symantec](#symantec).__
* __March 2003:__ VeriSign is found to have issued a fraudulent code signing certificate in the name of Microsoft Corporation. This allows an attacker to pretend that their software was verified and signed by Microsoft. ([source](
* __2010:__ Verisign is compromised, and undisclosed information is obtained by the attackers. ([source](