Where
-Infinity
0
Severity
6.5
AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths github.com/eclipse-keypont/crypto11 <= 1.6.8, github.com/ThalesGroup/crypto11 <= 1.7.0-rc1 and github.com/ThalesIgnite/crypto11 <= 1.2.5), the key-pair and certificate lookup functions (FindKeyPair, FindKeyPairs, FindKeyPairsWithAttributes, FindAllKeyPairs, the FindRSAKeyPair family and FindAllPairedCertificates) pair a private key with a public key object, or with a certificate, by CKAID/CKALABEL alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's CKAID and label, and crypto11 may return it as that key's public half. An application that publishes or trusts Signer.Public() (a JWKS endpoint, a key registry, authorizedkeys, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the private key has no CKAID, pairing a label-only private key with the first public key of its type on the token.

The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later.

First published (updated )
Severity
6.5
AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths github.com/eclipse-keypont/crypto11 <= 1.6.8, github.com/ThalesGroup/crypto11 <= 1.7.0-rc1 and github.com/ThalesIgnite/crypto11 <= 1.2.5), the key-pair and certificate lookup functions (FindKeyPair, FindKeyPairs, FindKeyPairsWithAttributes, FindAllKeyPairs, the FindRSAKeyPair family and FindAllPairedCertificates) pair a private key with a public key object, or with a certificate, by CKAID/CKALABEL alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's CKAID and label, and crypto11 may return it as that key's public half. An application that publishes or trusts Signer.Public() (a JWKS endpoint, a key registry, authorizedkeys, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the private key has no CKAID, pairing a label-only private key with the first public key of its type on the token.

The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later.

First published (updated )
Severity
5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

In github.com/eclipse-keypont/crypto11/v2 versions >= 2.0.0-rc3, <= 2.0.0-rc8, the ML-KEM key-pair lookup functions (FindMLKEMKeyPair, FindMLKEMKeyPairs, FindMLKEMKeyPairsWithAttributes) locate the public half of an ML-KEM key pair by CKAID/CKALABEL and never verify it against the private key. In addition, the "ID only" fallback search runs even when the private key has no CKAID, so the search template reduces to the public-key class and the ML-KEM key type and the first ML-KEM public key on the token is returned. Encapsulate() on the resulting key pair encrypts the fresh shared secret to that key, so its owner — not the holder of the private key the caller looked up — can recover the secret. An attacker who can open an unauthenticated session on the token and plant a public CKKMLKEM object carrying the victim's CKAID/CKALABEL receives the shared secrets for encapsulations performed through the substituted key pair, compromising the confidentiality of those secrets and of everything protected by keys derived from them. The v1 module paths have no ML-KEM support and are not affected.

First published (updated )
Severity
5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

In github.com/eclipse-keypont/crypto11/v2 versions >= 2.0.0-rc3, <= 2.0.0-rc8, the ML-KEM key-pair lookup functions (FindMLKEMKeyPair, FindMLKEMKeyPairs, FindMLKEMKeyPairsWithAttributes) locate the public half of an ML-KEM key pair by CKAID/CKALABEL and never verify it against the private key. In addition, the "ID only" fallback search runs even when the private key has no CKAID, so the search template reduces to the public-key class and the ML-KEM key type and the first ML-KEM public key on the token is returned. Encapsulate() on the resulting key pair encrypts the fresh shared secret to that key, so its owner — not the holder of the private key the caller looked up — can recover the secret. An attacker who can open an unauthenticated session on the token and plant a public CKKMLKEM object carrying the victim's CKAID/CKALABEL receives the shared secrets for encapsulations performed through the substituted key pair, compromising the confidentiality of those secrets and of everything protected by keys derived from them. The v1 module paths have no ML-KEM support and are not affected.

First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203