Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message…
openssl·CWE-354·Published 2026-06-09
Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery. Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability. If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file that will be accepted with a 1 in 256 probability. That would then cause the service to accept a certificate and private key controlled by the attacker. The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery. Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability. If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file that will be accepted with a 1 in 256 probability. That would then cause the service to accept a certificate and private key controlled by the attacker. The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Resumen del problema: El procesamiento de archivos PKCS#12 no realiza una validación de entrada suficiente para archivos que utilizan el mecanismo de integridad Password-Based Message Authentication Code 1 (PBMAC1), lo que permite la falsificación de un certificado y una clave privada. Resumen del impacto: Un atacante suplantando a un usuario puede hacer que un servicio que lee archivos PKCS#12 acepte certificados y claves privadas falsificados con una probabilidad de 1 entre 256. Si un servicio que acepta archivos PKCS#12 está utilizando contraseñas para la autenticación de los archivos recibidos, el atacante puede crear archivos PKCS#12 sin cifrar que utilizan autenticación PBMAC1 que especifica una clave HMAC de solo un byte, permitiéndoles crear un archivo que será aceptado con una probabilidad de 1 entre 256. Eso entonces haría que el servicio acepte un certificado y una clave privada controlados por el atacante. Los módulos FIPS no se ven afectados por este problema, ya que el código afectado está fuera del límite del módulo FIPS de OpenSSL.
| Version | Type | Source | Base | Exp | Impact | Vector |
|---|---|---|---|---|---|---|
| 3.1 | Primary | cve.org | 7.4 | — | — | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| 3.1 | Primary | cve.org | 7.4 | — | — | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| 3.1 | Secondary | NVD | 7.4 | 2.2 | 5.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |