Headline
GHSA-frqx-jfcm-6jjr: malformed proposed intoto entries can cause a panic
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
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-33199
malformed proposed intoto entries can cause a panic
Moderate severity GitHub Reviewed Published May 26, 2023 in sigstore/rekor
Package
gomod github.com/sigstore/rekor (Go)
Affected versions
< 1.2.0
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
References
- GHSA-frqx-jfcm-6jjr
- sigstore/rekor@140c5ad
Published to the GitHub Advisory Database
May 26, 2023
Related news
Rekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software projects supply chain. 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. This has been fixed in v1.2.0 of Rekor. Users are advised to upgrade. There are no known workarounds for this vulnerability.