Infinite recursion (CPU denial-of-service) in JOSE.JWK.shared_secret/2 on mismatched key types
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.11.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The JOSE library for Erlang and Elixir, specifically its JWK shared-secret (ECDH) derivation function, is affected. When two keys of mismatched types are passed in, the function can enter an endless loop that never returns, so an attacker supplying a crafted key can consume CPU indefinitely and cause a denial of service in applications that use it without validating peer keys first.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
jose_jwk:shared_secret/2 (exposed in Elixir as JOSE.JWK.shared_secret/2) derives an ECDH shared secret from two JWKs. Its first function clause only matches when both JWKs carry the same key type (kty) module, and its fallback clause re-invokes itself as shared_secret(from(YourJWK), from(MyJWK)). Because from/1 returns an already-parsed jose_jwk record unchanged, passing two JWKs whose key types differ (for example an EC key and an RSA key) makes the fallback clause re-enter with identical arguments, producing an unbounded tail-recursive loop that never returns and never crashes. An application that derives a shared secret from an externally supplied peer public key without first checking that the peer key's type and curve match its own key can be driven into this loop by an attacker-controlled JWK, pinning an Erlang scheduler at 100% CPU. Repeated requests exhaust the available schedulers, resulting in a denial of service. This issue affects jose: from 1.5.0 before 1.11.13.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- jose
From 1.5.0 · fixed in 1.11.13
- potatosalad/erlang-jose
From 7b80b9f55b9898e1a6901ce136061b241b021d7c · fixed in 26182a7de63b91550035d3f08741f7d17f1f675a
- joseHex
From 1.5.0 · fixed in 1.11.13