{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-41949 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-41949 is a low-severity authentication bypass vulnerability in biscuit-auth biscuit-rust, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41949 and fix it if it is affected.\n\nWhat it is: CVE-2024-41949 is a low-severity authentication bypass vulnerability in biscuit-auth biscuit-rust, published on 1 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-41949 in the wild and no public exploit code.\n\nAffected product: biscuit-auth biscuit-rust. 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-41949/ (Markdown: https://insights.sbomify.com/CVE-2024-41949/index.md)","id":"CVE-2024-41949","markdown":"https://insights.sbomify.com/CVE-2024-41949/index.md","name":"CVE-2024-41949","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust authentication library","requires_auth":"high_privilege","summary":"A malicious user can trick a third-party authority into trusting a wrong keypair, leading to authentication bypass and privilege escalation in microservices using biscuit-rust.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"biscuit-auth","vendor":"biscuitsec"}],"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-269","name":"Improper Privilege Management"}],"description":"biscuit-rust is the Rust 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.","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":"biscuit-rust vulnerable to public key confusion in third party block","id":"CVE-2024-41949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Insecure Jinja2 templates rendered in Haystack Components can lead to RCE","id":"CVE-2024-41950"},"packages":[],"prev":{"headline":"biscuit-java vulnerable to public key confusion in third party block","id":"CVE-2024-41948"},"products":["biscuit-rust"],"published":"2024-08-01","related":[{"cvss_score":9.8,"headline":"Signature forgery in Biscuit","id":"CVE-2022-31053","kev_date_added":null,"published":"2022-06-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02","vendors":["biscuit-auth"]},"summary":"A malicious user can trick a third-party authority into trusting a wrong keypair, leading to authentication bypass and privilege escalation in microservices using biscuit-rust.","url":"https://insights.sbomify.com/CVE-2024-41949/"}