CVE-2024-41948
CVE-2024-41948 is a low-severity vulnerability in Biscuitsec Biscuit-java with a CVSS 3.x base score of 3.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1259.
Key facts
- Severity: Low (CVSS 3.x base score 3.0)
- EPSS exploit prediction: 0% (20th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2024-2267
- Weakness: CWE-1259
- Affected product: Biscuitsec Biscuit-java
- Published:
- Last modified:
Description
biscuit-java is the java 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. This vulnerability is fixed in 4.0.0.
Frequently asked questions
- What is CVE-2024-41948?
- biscuit-java is the java 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. This vulnerability is fixed in 4.0.0.
- How severe is CVE-2024-41948?
- CVE-2024-41948 has a CVSS 3.x base score of 3.0, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
- Is CVE-2024-41948 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-41948?
- CVE-2024-41948 affects Biscuitsec Biscuit-java. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-41948?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2024-41948 have an EU (EUVD) identifier?
- Yes. CVE-2024-41948 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2267.
- When was CVE-2024-41948 published?
- CVE-2024-41948 was published on 2024-08-01 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:biscuitsec:biscuit-java:*:*:*:*:*:*:*:*
Other CWE-1259 vulnerabilities
- CVE-2024-36533 — Critical (CVSS 9.8): Insecure permissions in volcano v1.8.2 allows attackers to access sensitive data and escalate privileges by obtaining…
- CVE-2024-29371 — High (CVSS 7.5): In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web…
- CVE-2026-25700 — High (CVSS 7.2): Improper Restriction of Security Token Assignment vulnerability in Apache Answer. This issue affects Apache Answer:…
- CVE-2025-56207 — Medium (CVSS 6.5): A security flaw in the '_transfer' function of a smart contract implementation for Money Making Opportunity (MMO), an…
- CVE-2024-4598 — Medium (CVSS 6.5): An information disclosure vulnerability exists in multiple WSO2 products due to improper implementation of the enrich…
- CVE-2025-51306 — Medium (CVSS 6.5): In Gatling Enterprise versions below 1.25.0, a user logging-out can still use his session token to continue using the…