Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/sigstore/sigstore-conformance/pull/139
- https://github.com/sigstore/sigstore-java/commit/23fb4885e6704a5df4977f7acf253a7
- https://github.com/sigstore/sigstore-java/security/advisories/GHSA-jp26-88mw-89q
FAQ
What is CVE-2024-54140?
CVE-2024-54140 is a documented vulnerability. 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 chec...
How severe is CVE-2024-54140?
CVSS scoring is not yet available for CVE-2024-54140. Check NVD for updates.
Is there a patch for CVE-2024-54140?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.