Possible NULL Dereference When Processing CMS KeyAgreeRecipientInfo
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in OpenSSL 1.0.2zp, OpenSSL 1.1.1zg, OpenSSL 3.0.20 and 4 more.
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| OpenSSL | OpenSSL | >=1.0.2 <1.0.2zp, >=1.1.1 <1.1.1zg, >=3.0.0 <3.0.20, >=3.3.0 <3.3.7, >=3.4.0 <3.4.5, >=3.5.0 <3.5.6, >=3.6.0 <3.6.2 | 1.0.2zp, 1.1.1zg, 3.0.20, 3.3.7, 3.4.5, 3.5.6, 3.6.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in OpenSSL, strongest first
Embed
A live severity badge for an advisory, README or ticket