{"answers":{"affected":"2 open source packages ship an affected version, including dev.sigstore:sigstore-java.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54140 exists.","fix":"Upgrade dev.sigstore:sigstore-java to 1.2.0 or later.","what":"CVE-2024-54140 is a low-severity vulnerability in sigstore-java, published on 5 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-54140 and fix it if it is affected.\n\nWhat it is: CVE-2024-54140 is a low-severity vulnerability in sigstore-java, published on 5 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54140 exists.\n\nAffected packages and fixed versions:\n- dev.sigstore:sigstore-java (Maven): affected all versions; fixed in 1.2.0\n- dev.sigstore:sigstore-java (Maven): affected all versions; fixed in 1.2.0\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-54140/ (Markdown: https://insights.sbomify.com/CVE-2024-54140/index.md)","id":"CVE-2024-54140","markdown":"https://insights.sbomify.com/CVE-2024-54140/index.md","name":"CVE-2024-54140","record":{"aliases":["GHSA-jp26-88mw-89qr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java Sigstore client","requires_auth":"none","summary":"Insufficient bundle verification in sigstore-java allows bypassing log integrity checks, potentially hiding compromised log views from monitors.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"sigstore-java is a sigstore java client for interacting with sigstore infrastructure. sigstore-java has insufficient verification for a situation where a bundle provides a invalid signature for a checkpoint. This bug impacts clients using any variation of KeylessVerifier.verify(). Currently checkpoints are only used to ensure the root hash of an inclusion proof was provided by the log in question. Failing to validate that means a bundle may provide an inclusion proof that doesn't actually correspond to the log in question. This may eventually lead a monitor/witness being unable to detect when a compromised logs are providing different views of themselves to different clients. There are other mechanisms right now that mitigate this, such as the signed entry timestamp. Sigstore-java currently requires a valid signed entry timestamp. By correctly verifying the signed entry timestamp we can make certain assertions about the log signing the log entry (like the log was aware of the artifact signing event and signed it). Therefore the impact on clients that are not monitors/witnesses is very low. This vulnerability is fixed in 1.2.0.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"sigstore-java has a vulnerability with bundle verification","id":"CVE-2024-54140","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"phpMyFAQ Generates an Error Message Containing Sensitive Information if database server is not available","id":"CVE-2024-54141"},"packages":[{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":null,"source":"GHSA-jp26-88mw-89qr"},{"ecosystem":"Maven","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":"pkg:maven/dev.sigstore/sigstore-java","source":"GHSA-jp26-88mw-89qr"}],"prev":{"headline":"Combodo iTop vulnerable to XSS leading to CSRF breach on _table_id parameter","id":"CVE-2024-54139"},"products":["sigstore-java"],"published":"2024-12-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-10","vendors":["sigstore"]},"summary":"Insufficient bundle verification in sigstore-java allows bypassing log integrity checks, potentially hiding compromised log views from monitors.","url":"https://insights.sbomify.com/CVE-2024-54140/"}