There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
2023-02-08T20:15:24.267
2025-03-20T21:15:16.550
Modified
CVSSv3.1: 7.4 (HIGH)
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | openssl | openssl | < 1.0.2zg | Yes |
Application | openssl | openssl | < 1.1.1t | Yes |
Application | openssl | openssl | < 3.0.8 | Yes |
Application | stormshield | stormshield_management_center | < 3.3.3 | Yes |
Application | stormshield | stormshield_network_security | < 2.7.11 | Yes |
Application | stormshield | stormshield_network_security | < 3.7.34 | Yes |
Application | stormshield | stormshield_network_security | < 3.11.22 | Yes |
Application | stormshield | stormshield_network_security | < 4.3.16 | Yes |
Application | stormshield | stormshield_network_security | < 4.6.3 | Yes |