{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-42350 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-42350 is a low-severity authentication bypass vulnerability in biscuit-auth biscuit, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-42350 and fix it if it is affected.\n\nWhat it is: CVE-2024-42350 is a low-severity authentication bypass vulnerability in biscuit-auth biscuit, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-42350 in the wild and no public exploit code.\n\nAffected product: biscuit-auth biscuit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-42350/ (Markdown: https://insights.sbomify.com/CVE-2024-42350/index.md)","id":"CVE-2024-42350","markdown":"https://insights.sbomify.com/CVE-2024-42350/index.md","name":"CVE-2024-42350","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Biscuit authorization library","requires_auth":"high_privilege","summary":"A malicious user can trick a third-party authority into generating tokens trusting the wrong keypair, bypassing authorization checks in Biscuit implementations.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"Biscuit is an authorization token with decentralized verification, offline attenuation and strong security policy enforcement based on a logic language. 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: 1. the public key of the previous block (used in the signature), 2. 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. Tokens with third-party blocks containing `trusted` annotations generated through a third party block request. This has been addressed in version 4 of the specification. Users are advised to update their implementations to conform. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Public key confusion in third party block in Biscuit","id":"CVE-2024-42350","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Possible Data Tampering \u0026 Loss of Public Datasets in Galaxy","id":"CVE-2024-42351"},"packages":[],"prev":{"headline":"FOG has a Log Information Disclosure","id":"CVE-2024-42349"},"products":["biscuit"],"published":"2024-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["biscuit-auth"]},"summary":"A malicious user can trick a third-party authority into generating tokens trusting the wrong keypair, bypassing authorization checks in Biscuit implementations.","url":"https://insights.sbomify.com/CVE-2024-42350/"}