CVE-2024-55655: Sigstore Sigstore Has Insufficient Validation Of Vulnerability
LOWCVE-2024-55655 is a LOW sigstore has insufficient validation of vulnerability (CWE-20: Improper Input Validation) affecting Sigstore libraries in the PyPI ecosystem. The issue involves sigstore has insufficient validation of integration timestamp during verification. Remediation is available by upgrading affected packages to version 3.6.0.
CVE-2024-55655 at a Glance
How to Fix CVE-2024-55655
To remediate this vulnerability, upgrade all affected Sigstore dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install sigstore>=3.6.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show sigstore
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2024-55655, inspect your installed packages using pip:
pip show sigstore
Analyze the terminal output to locate any version of Sigstore in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.6.0), your application is affected.
Note: The pip show sigstore command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Sigstore, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-55655 Affected Sigstore Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
sigstore
|
PyPI |
≥ 2.0.0
< 3.6.0
|
3.6.0
|
References
Frequently Asked Questions
What is CVE-2024-55655?
Which Sigstore versions are affected?
What version fixes CVE-2024-55655?
Is sigstore affected?
What CWE is associated with CVE-2024-55655?
How can I check PyPI dependencies for CVE-2024-55655?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hhfg-fwrw-87w7",
"modified" : "2024-12-11T18:42:00Z",
"published" : "2024-12-11T18:42:00Z",
"aliases" : [ "CVE-2024-55655" ],
"summary" : "sigstore has insufficient validation of integration timestamp during verification",
"details" : "### Summary\n\nVersions 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.\n\nThis does not affect \"v1\" bundles, as the \"v1\" bundle format always requires an inclusion promise.\n\n### Details\n\nSigstore uses signed time to support verification of signatures made against short-lived signing keys. \n\n### Impact\n\nThe 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).\n\nSeparately, 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.\n",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "sigstore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "3.6.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore-python/security/advisories/GHSA-hhfg-fwrw-87w7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-55655"
}, {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore-python/commit/300b502ae99ebfaace124f1f4e422a6a669369cf"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sigstore/sigstore-python"
}, {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore-python/releases/tag/v3.6.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-325" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2024-12-11T18:42:00Z",
"nvd_published_at" : "2024-12-10T23:15:06Z"
}
}