In `github.com/eclipse-keypont/crypto11/v2` versions `>= 2.0.0-rc3, <= 2.0.0-rc8`, the ML-KEM key-pair lookup functions (`FindMLKEMKeyPair`…
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 `CKA_ID`/`CKA_LABEL` and never verify it against the private key. In addition, the "ID only" fallback search runs even when the private key has no `CKA_ID`, 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 — c
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Eclipse Foundation
- Product
- Eclipse KeyPont
- CVSS v3.1
- 5.5 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Weakness
- CWE-345
- NVD status
- Received
Why it ranks 3 (Routine)
- CVSS v3.1 5.5 medium
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.