{"answers":{"affected":"3 open source packages ship an affected version, including sigstore.","exploited":"There is no known exploitation of CVE-2024-55655 in the wild and no public exploit code.","fix":"Upgrade sigstore to 3.6.0 or later.","what":"CVE-2024-55655 is a low-severity vulnerability in sigstore-python, published on 10 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-55655 and fix it if it is affected.\n\nWhat it is: CVE-2024-55655 is a low-severity vulnerability in sigstore-python, published on 10 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-55655 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sigstore (PyPI): affected from 2.0.0; fixed in 3.6.0\n- sigstore (PyPI): affected from 2.0.0; fixed in 3.6.0\n- sigstore (PyPI): affected from 2.0.0; fixed in 3.6.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-55655/ (Markdown: https://insights.sbomify.com/CVE-2024-55655/index.md)","id":"CVE-2024-55655","markdown":"https://insights.sbomify.com/CVE-2024-55655/index.md","name":"CVE-2024-55655","record":{"aliases":["GHSA-hhfg-fwrw-87w7","PYSEC-2026-1923"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python signature verification library","requires_auth":"none","summary":"Attackers can manipulate integration timestamps in Sigstore bundles, potentially causing denial of service, though other controls prevent signature impersonation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-325","name":"Missing Cryptographic Step"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"sigstore-python is a Python tool for generating and verifying Sigstore signatures. Versions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the \"integration time\" present in \"v2\" and \"v3\" bundles during the verification flow: the \"integration time\" is verified *if* a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect \"v1\" bundles, as the \"v1\" bundle format always requires an inclusion promise.\n\nSigstore uses signed time to support verification of signatures made against short-lived signing keys. The impact and severity of this weakness is *low*, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a *new* entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable.","ecosystems":["PyPI"],"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":"sigstore-python has insufficient validation of integration timestamp during verification","id":"CVE-2024-55655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"RedisBloom Integer Overflow Remote Code Execution Vulnerability","id":"CVE-2024-55656"},"packages":[{"ecosystem":"PyPI","fixed":["3.6.0"],"introduced":["2.0.0"],"last_affected":[],"package":"sigstore","purl":null,"source":"GHSA-hhfg-fwrw-87w7"},{"ecosystem":"PyPI","fixed":["3.6.0"],"introduced":["2.0.0"],"last_affected":[],"package":"sigstore","purl":"pkg:pypi/sigstore","source":"GHSA-hhfg-fwrw-87w7"},{"ecosystem":"PyPI","fixed":["3.6.0"],"introduced":["2.0.0"],"last_affected":[],"package":"sigstore","purl":"pkg:pypi/sigstore","source":"PYSEC-2026-1923"}],"prev":{"headline":"pwndoc's UnhandledPromiseRejection on audits causes Denial of Service (DoS)","id":"CVE-2024-55653"},"products":["sigstore-python"],"published":"2024-12-10","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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-11","vendors":["sigstore"]},"summary":"Attackers can manipulate integration timestamps in Sigstore bundles, potentially causing denial of service, though other controls prevent signature impersonation.","url":"https://insights.sbomify.com/CVE-2024-55655/"}