CVE-2024-41949: Biscuit auth Biscuit-auth Vulnerable To Public Key Vulnerability

LOW
Advisory Identifier: GHSA-p9w4-585h-g3c7
CVSS 3.0
CWE-269
Published
Advisory Summary

CVE-2024-41949 is a LOW (CVSS 3.0) biscuit-auth vulnerable to public key vulnerability (CWE-269: Improper Privilege Management) affecting Biscuit auth libraries in the crates.io ecosystem. The issue involves biscuit-auth vulnerable to public key confusion in third party block. Remediation is available by upgrading affected packages to version 5.0.0.

CVE-2024-41949 at a Glance

CVE Identifier CVE-2024-41949
GHSA Identifier GHSA-p9w4-585h-g3c7
Severity LOW
CVSS v3.1 Base Score 3.0
CWE Classification CWE-269: Improper Privilege Management
Affected Product Biscuit auth
Package Ecosystem crates.io
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-41949

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

biscuit-auth fixed: 5.0.0
Upgrade biscuit-auth to 5.0.0
Verify Direct and Transitive Dependencies

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

inspect dependencies for biscuit-auth

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-41949, inspect your project dependencies for Biscuit auth:

inspect dependencies for biscuit-auth

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

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Biscuit auth, 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

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`. ### Impact Tokens with third-party blocks containing `trusted` annotations generated through a third party block request

CVE-2024-41949 Affected Biscuit auth Versions

1 component(s)
Fixed Versions:
5.0.0
Product / Package Ecosystem Affected Versions Fixed Version
biscuit-auth
crates.io
≥ 4.0.0
< 5.0.0
5.0.0

References

Frequently Asked Questions

What is CVE-2024-41949?
CVE-2024-41949 is a security vulnerability in Biscuit auth involving biscuit-auth vulnerable to public key confusion in third party block under CWE-269: Improper Privilege Management.
Which Biscuit auth versions are affected?
Affected versions include releases prior to 5.0.0 across affected packages: biscuit-auth.
What version fixes CVE-2024-41949?
Upgrading to 5.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is biscuit-auth affected?
Yes, biscuit-auth is affected in releases prior to 5.0.0. Upgrade your dependency to 5.0.0 or later.
What is the CVSS score of CVE-2024-41949?
CVE-2024-41949 has a CVSS v3.1 base score of 3.0 (LOW) 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-41949?
CVE-2024-41949 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check crates.io dependencies for CVE-2024-41949?
Run the dependency tree command: 'inspect dependencies for biscuit-auth'. 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-p9w4-585h-g3c7",
  "modified" : "2024-08-05T21:14:26Z",
  "published" : "2024-07-31T21:15:41Z",
  "aliases" : [ "CVE-2024-41949" ],
  "summary" : "biscuit-auth vulnerable to public key confusion in third party block",
  "details" : "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:\n\n- the public key of the previous block (used in the signature)\n- the public keys part of the token symbol table (for public key interning in datalog expressions)\n\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\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### Impact\n\nTokens with third-party blocks containing `trusted` annotations generated through a third party block request\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:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "biscuit-auth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "5.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/biscuit-auth/biscuit-rust/security/advisories/GHSA-p9w4-585h-g3c7"
  }, {
    "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-41949"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/biscuit-auth/biscuit-rust"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-07-31T21:15:41Z",
    "nvd_published_at" : "2024-08-01T22:15:28Z"
  }
}