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.
Metrics
Affected Vendors & Products
References
History
Tue, 10 Dec 2024 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Sigstore
Sigstore sigstore-java |
|
CPEs | cpe:2.3:a:sigstore:sigstore-java:*:*:*:*:*:*:*:* | |
Vendors & Products |
Sigstore
Sigstore sigstore-java |
|
Metrics |
ssvc
|
Thu, 05 Dec 2024 22:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | sigstore-java has a vulnerability with bundle verification | |
Weaknesses | CWE-20 | |
References |
| |
Metrics |
cvssV4_0
|
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2024-12-05T22:08:37.195Z
Updated: 2024-12-10T14:55:08.151Z
Reserved: 2024-11-29T18:02:16.755Z
Link: CVE-2024-54140
Vulnrichment
Updated: 2024-12-10T14:55:03.418Z
NVD
Status : Received
Published: 2024-12-05T22:15:20.400
Modified: 2024-12-05T22:15:20.400
Link: CVE-2024-54140
Redhat
No data.