post: fixes for CVE-2025-15467

Author: srmish-jfrog

post/potential-rce-vulnerabilityin-openssl-cve-2025-15467.md

@@ -26,14 +26,29 @@ FIPS modules in 3.6, 3.5, 3.4, 3.3, and 3.0 are not affected, as the CMS impleme
 
 ## Reproducing CVE-2025-15467
 
-**Our research team has managed to reproduce the vulnerability** by calling the [**CMS\_Decrypt**](https://docs.openssl.org/3.2/man3/CMS_decrypt/) API directly, which means that OpenSSL applications that directly call this API are vulnerable to CVE-2025-15467.
+**Our research team has managed to reproduce the vulnerability** by calling the [**CMS\_Decrypt**](https://docs.openssl.org/3.2/man3/CMS_decrypt/) API directly -
 ![](/img/RealTimePostImage/post/openssl/image2.png)
 
-Exploitation can also be achieved when applications are using the `openssl cms` CLI tool to decrypt untrusted data:
 
-```shell
-openssl cms -decrypt -in untrusted_data.pem
-```
+
+We have observed the following cases to be vulnerable to CVE-2025-15467 -
+
+A. OpenSSL-based applications that call any of the following APIs -
+
+* `CMS_RecipientInfo_decrypt`
+* `CMS_decrypt_set1_pkey_and_peer`
+* `CMS_decrypt_set1_pkey`
+* `CMS_decrypt`
+* `PKCS7_decrypt`
+* `CMS_EnvelopedData_decrypt`
+
+
+
+B. Applications that invoke any of the following OpenSSL tools -
+* `openssl cms`
+* `openssl smime`
+
+
 
 Note that this is only an initial assessment and more attack vectors are likely to be relevant, stay tuned as we update this blog.