Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.biscuitsec:biscuit

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.1MavenPublished

    biscuit-java vulnerable to public key confusion in third party block

    CVE-2024-41948 · GHSA-5hcj-rwm6-xmw4

    Affected
    • Maven org.biscuitsec:biscuit >= 3.0.0, < 4.0.0
    Fixed in
    4.0.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 4.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →