CVE-2024-41948: Biscuit Biscuit-java Vulnerable To Public Key Vulnerability

MODERATE
Advisory Identifier: GHSA-5hcj-rwm6-xmw4
CVSS 3.0
CWE-1259
Published
Advisory Summary

CVE-2024-41948 is a MODERATE (CVSS 3.0) biscuit-java vulnerable to public key vulnerability (CWE-1259: Improper Restriction of Security Token Assignment) affecting Biscuit libraries in the Maven ecosystem. The issue involves biscuit-java vulnerable to public key confusion in third party block. Remediation is available by upgrading affected packages to version 4.0.0.

CVE-2024-41948 at a Glance

CVE Identifier CVE-2024-41948
GHSA Identifier GHSA-5hcj-rwm6-xmw4
Severity MODERATE
CVSS v3.1 Base Score 3.0
CWE Classification CWE-1259: Improper Restriction of Security Token Assignment
Affected Product Biscuit
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2024-41948

To remediate this vulnerability, upgrade all affected Biscuit dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.biscuitsec:biscuit fixed: 4.0.0
<dependency>
    <groupId>org.biscuitsec</groupId>
    <artifactId>biscuit</artifactId>
    <version>4.0.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.biscuitsec

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2024-41948, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.biscuitsec

Analyze the terminal output to locate any version of Biscuit in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.biscuitsec command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1259: Improper Restriction of Security Token Assignment, where the system-on-a-chip (soc) implements a security token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. however, the security tokens are improperly protected. In Biscuit, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Tokens with third-party blocks containing trusted annotations generated through a third party block request. Due to implementation issues in biscuit-java, third party block support in published versions is inoperating. Nevertheless, to synchronize with other implementations, we publish this advisory and the related fix. ### Description 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: the public key of the previous block (used in the signature) 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. Consider the following example (nominal case) * Authority A emits the following token: `check if thirdparty("b") trusting ${pubkeyB}` * The well-behaving holder then generates a third-party block request based on the token and sends it to third-party authority B * Third-party B generates the following third-party block `thirdparty("b"); check if thirdparty("c") trusting ${pubkeyC}` * The token holder now must obtain a third-party block from third party C to be able to use the token Now, with a malicious user: * Authority A emits the following token: `check if thirdparty("b") trusting ${pubkeyB}` * The holder then attenuates the token with the following third party block `thirdparty("c")`, signed with a keypair pubkeyD, privkeyD) they generate * The holder then generates a third-party block request based on this token, but alter the `ThirdPartyBlockRequest` publicKeys field and replace pubkeyD with pubkeyC * Third-party B generates the following third-party block `thirdparty("b"); check if thirdparty("c") trusting ${pubkeyC}` * Due to the altered symbol table, the actual meaning of the block is `thirdparty("b"); check if thirdparty("c") trusting ${pubkeyD}` * The attacker can now use the token without obtaining a third-party block from C. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ ### References _Are there any links users can visit to find out more?_

CVE-2024-41948 Affected Biscuit Versions

1 component(s)
Fixed Versions:
4.0.0
Product / Package Ecosystem Affected Versions Fixed Version
org.biscuitsec:biscuit
Maven
≥ 3.0.0
< 4.0.0
4.0.0

References

Frequently Asked Questions

What is CVE-2024-41948?
CVE-2024-41948 is a security vulnerability in Biscuit involving biscuit-java vulnerable to public key confusion in third party block under CWE-1259: Improper Restriction of Security Token Assignment.
Which Biscuit versions are affected?
Affected versions include releases prior to 4.0.0 across affected packages: org.biscuitsec:biscuit.
What version fixes CVE-2024-41948?
Upgrading to 4.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is biscuit affected?
Yes, org.biscuitsec:biscuit is affected in releases prior to 4.0.0. Upgrade your dependency to 4.0.0 or later.
What is the CVSS score of CVE-2024-41948?
CVE-2024-41948 has a CVSS v3.1 base score of 3.0 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N.
What CWE is associated with CVE-2024-41948?
CVE-2024-41948 is classified under CWE-1259: Improper Restriction of Security Token Assignment (The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.).
How can I check Maven dependencies for CVE-2024-41948?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.biscuitsec'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5hcj-rwm6-xmw4",
  "modified" : "2024-11-18T16:26:57Z",
  "published" : "2024-07-31T18:48:40Z",
  "aliases" : [ "CVE-2024-41948" ],
  "summary" : "biscuit-java vulnerable to public key confusion in third party block",
  "details" : "### Impact\nTokens with third-party blocks containing trusted annotations generated through a third party block request. Due to implementation issues in biscuit-java,  third party block support in published versions is inoperating. Nevertheless, to synchronize with other implementations, we publish this advisory and the related fix.\n\n### Description\nThird-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:\n\nthe public key of the previous block (used in the signature)\nthe public keys part of the token symbol table (for public key interning in datalog expressions)\nA third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.\n\nConsider the following example (nominal case)\n* Authority A emits the following token: `check if thirdparty(\"b\") trusting ${pubkeyB}`\n* The well-behaving holder then generates a third-party block request based on the token and sends it to third-party authority B\n* Third-party B generates the following third-party block `thirdparty(\"b\"); check if thirdparty(\"c\") trusting ${pubkeyC}`\n* The token holder now must obtain a third-party block from third party C to be able to use the token\n\nNow, with a malicious user:\n* Authority A emits the following token: `check if thirdparty(\"b\") trusting ${pubkeyB}`\n* The holder then attenuates the token with the following third party block `thirdparty(\"c\")`, signed with a keypair pubkeyD, privkeyD) they generate\n* The holder then generates a third-party block request based on this token, but alter the `ThirdPartyBlockRequest` publicKeys field and replace pubkeyD with pubkeyC\n* Third-party B generates the following third-party block `thirdparty(\"b\"); check if thirdparty(\"c\") trusting ${pubkeyC}`\n* Due to the altered symbol table, the actual meaning of the block is `thirdparty(\"b\"); check if thirdparty(\"c\") trusting ${pubkeyD}`\n* The attacker can now use the token without obtaining a third-party block from C.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### References\n_Are there any links users can visit to find out more?_\n\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.biscuitsec:biscuit"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "4.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/biscuit-auth/biscuit-java/security/advisories/GHSA-5hcj-rwm6-xmw4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/biscuit-auth/biscuit/security/advisories/GHSA-rgqv-mwc3-c78m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-41948"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/biscuit-auth/biscuit-java/commit/2e05e7b3f8f2aae38f33294f19419e2d638cb564"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/biscuit-auth/biscuit-java"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/biscuit-auth/biscuit-java/releases/tag/4.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1259" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-07-31T18:48:40Z",
    "nvd_published_at" : "2024-08-01T22:15:28Z"
  }
}