Authorization bypass via forged public-key symbol table
Published Aug 1, 2024 · Updated Aug 7, 2024
Public-key confusion in Biscuit Java 3.0.0 through 3.0.2 allows remote authenticated users to bypass third-party authorization. ThirdPartyBlockRequest accepts an attacker-altered publicKeys symbol table, causing generated Datalog to trust the attacker's keypair instead of the requested key. Exploitation requires a holder able to attenuate a valid token and submit the forged request, although the maintainer states that published third-party block support is inoperative.
Summary
What happened
Public-key confusion in Biscuit Java 3.0.0 through 3.0.2 allows remote authenticated users to bypass third-party authorization. ThirdPartyBlockRequest accepts an attacker-altered publicKeys symbol table, causing generated Datalog to trust the attacker's keypair instead of the requested key. Exploitation requires a holder able to attenuate a valid token and submit the forged request, although the maintainer states that published third-party block support is inoperative.
The record
- CVE
- CVE-2024-41948
- Published
- Aug 1, 2024
- Updated
- Aug 7, 2024
- Vendor
- Eclipse Biscuit
- Product
- Biscuit Java
- Classifications
- CWE-1259, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 7, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 4.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo