{"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-53267 exists.","fix":"Upgrade dev.sigstore:sigstore-java to 1.1.0 or later.","what":"CVE-2024-53267 is a medium-severity vulnerability in sigstore-java, published on 26 Nov 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-53267 and fix it if it is affected.\n\nWhat it is: CVE-2024-53267 is a medium-severity vulnerability in sigstore-java, published on 26 Nov 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-53267 exists.\n\nAffected packages and fixed versions:\n- dev.sigstore:sigstore-java (Maven): affected from 1.0.0; fixed in 1.1.0\n- dev.sigstore:sigstore-java (Maven): affected from 1.0.0; fixed in 1.1.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-53267/ (Markdown: https://insights.sbomify.com/CVE-2024-53267/index.md)","id":"CVE-2024-53267","markdown":"https://insights.sbomify.com/CVE-2024-53267/index.md","name":"CVE-2024-53267","record":{"aliases":["GHSA-q4xm-6fjc-5f6w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java signing client","requires_auth":"low_privilege","summary":"Attackers can bypass transparency log verification in sigstore-java, allowing malicious artifacts to appear legitimately signed without proper logging proof.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"sigstore-java is a sigstore java client for interacting with sigstore infrastructure. sigstore-java has insufficient verification for a situation where a validly-signed but \"mismatched\" bundle is presented as proof of inclusion into a transparency log. This bug impacts clients using any variation of KeylessVerifier.verify(). The verifier may accept a bundle with an unrelated log entry, cryptographically verifying everything but fails to ensure the log entry applies to the artifact in question, thereby \"verifying\" a bundle without any proof the signing event was logged. This allows the creation of a bundle without fulcio certificate and private key combined with an unrelated but time-correct log entry to fake logging of a signing event. A malicious actor using a compromised identity may want to do this to prevent discovery via rekor's log monitors. The signer's identity will still be available to the verifier. The signature on the bundle must still be on the correct artifact for the verifier to pass. sigstore-gradle-plugin and sigstore-maven-plugin are not affected by this as they only provide signing functionality. This issue has been patched in v1.1.0 release with PR #856. All users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Vulnerability with bundle verification in sigstore-java","id":"CVE-2024-53267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Lack of validation on openExternal allows 1 click remote code execution in joplin","id":"CVE-2024-53268"},"packages":[{"ecosystem":"Maven","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":null,"source":"GHSA-q4xm-6fjc-5f6w"},{"ecosystem":"Maven","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":"pkg:maven/dev.sigstore/sigstore-java","source":"GHSA-q4xm-6fjc-5f6w"}],"prev":{"headline":"Cross-site Scripting (XSS) via topic titles when CSP disabled in Discourse","id":"CVE-2024-53266"},"products":["sigstore-java"],"published":"2024-11-26","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-11-26","vendors":["sigstore"]},"summary":"Attackers can bypass transparency log verification in sigstore-java, allowing malicious artifacts to appear legitimately signed without proper logging proof.","url":"https://insights.sbomify.com/CVE-2024-53267/"}