CVE-2024-41949 biscuit-rust vulnerable to public key confusion in third party block
A malicious user can trick a third-party authority into trusting a wrong keypair, leading to authentication bypass and privilege escalation in microservices using biscuit-rust.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-41949?
CVE-2024-41949 is a low-severity authentication bypass vulnerability in biscuit-auth biscuit-rust, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
biscuit-rust is the Rust implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a ThirdPartyBlock request can be sent, providing only the necessary info to generate a third-party block and to sign it, which includes the public key of the previous block (used in the signature) and the public keys part of the token symbol table (for public key interning in datalog expressions). A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.
Weakness: CWE-269
Which versions are affected by CVE-2024-41949?
It affects 1 product.
Products include Biscuitsec Biscuit-Auth.
How do I fix CVE-2024-41949?
Upgrade to a fixed version.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-41949 being exploited?
There is no known exploitation of CVE-2024-41949 in the wild and no public exploit code.