CVE-2024-53267Vulnerability with bundle verification in sigstore-java

Official 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.

Affected packages & fixed versions

Affected products (as reported)

References

• https://github.com/sigstore/sigstore-java/security/advisories/GHSA-q4xm-6fjc-5f6w x_refsource_CONFIRM
• https://github.com/sigstore/sigstore-conformance/pull/166 x_refsource_MISC
• https://github.com/sigstore/sigstore-java/pull/856 x_refsource_MISC