| Name |
Creating a Rogue Certification Authority Certificate |
|
| Likelyhood of attack |
Typical severity |
| Medium |
Very High |
|
| Summary |
An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. |
| Prerequisites |
Certification Authority is using a hash function with insufficient collision resistance to generate the certificate hash to be signed |
| Execution Flow |
| Step |
Phase |
Description |
Techniques |
| 1 |
Experiment |
[Craft Certificates] The adversary crafts two different, but valid X.509 certificates that when hashed with an insufficiently collision resistant hashing algorithm would yield the same value. |
|
| 2 |
Experiment |
[Send CSR to Certificate Authority] The adversary sends the CSR for one of the certificates to the Certification Authority which uses the targeted hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. |
|
| 3 |
Exploit |
[Insert Signed Blob into Unsigned Certificate] The adversary takes the signed blob and inserts it into the second X.509 certificate that the attacker generated. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob is valid in the second certificate. The result is two certificates that appear to be signed by a valid certificate authority despite only one having been signed. |
|
|
| Solutions | Certification Authorities need to stop using deprecated or cryptographically insecure hashing algorithms to hash the certificates that they are about to sign. Instead they should be using stronger hashing functions such as SHA-256 or SHA-512. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-290 |
Authentication Bypass by Spoofing |
| CWE-295 |
Improper Certificate Validation |
| CWE-327 |
Use of a Broken or Risky Cryptographic Algorithm |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-473 |
An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions. |
|