MEDIUM5.3

GHSA-frqx-jfcm-6jjr

malformed proposed intoto entries can cause a panic

Quick fix

GHSA-frqx-jfcm-6jjr — github.com/sigstore/rekor: upgrade to the fixed version with the command below.

go get github.com/sigstore/rekor@v1.2.0

Details

### Impact A malformed proposed entry of the `intoto/v0.0.2` type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal.

### Patches This is fixed in v1.2.0 of Rekor.

### Workarounds No

### References Discovered by OSS-Fuzz

Are you affected?

Enter the version of the package you're using.

Affected packages

Go/github.com/sigstore/rekor

Introduced in: 0Fixed in: 1.2.0

Fixgo get github.com/sigstore/rekor@v1.2.0

References

https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr[WEB]
https://nvd.nist.gov/vuln/detail/CVE-2023-33199[ADVISORY]
https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4[WEB]
https://github.com/sigstore/rekor[PACKAGE]