Improper validation of the server’s certificate chain in secure traffic scanning feature considered intermediate certificate signed using t…
Improper validation of the server’s certificate chain in secure traffic scanning feature considered intermediate certificate signed using the MD5 or SHA1 algorithm as trusted.
The product does not validate, or incorrectly validates, a certificate.
https://cwe.mitre.org/data/definitions/295.html →Open in CWE collection →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.
https://capec.mitre.org/data/definitions/459.html →Open in CAPEC collection →An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.
https://capec.mitre.org/data/definitions/475.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| endpoint_antivirus | * | Tracked |
| endpoint_security | * | Tracked |
| file_security | * | Tracked |
| internet_security | * | Tracked |
| mail_security | * | Tracked |
| nod32_antivirus | * | Tracked |
| security | * | Tracked |
| server_security | * | Tracked |
| smart_security | * | Tracked |