Headline
CVE-2023-33199: Merge pull request from GHSA-frqx-jfcm-6jjr · sigstore/rekor@140c5ad
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.
Commit
Permalink
Browse files
Browse the repository at this point in the history
* fix for GHSA-frqx-jfcm-6jjr
Signed-off-by: Bob Callaway bcallaway@google.com
* add defensive check
Signed-off-by: Bob Callaway bcallaway@google.com
* add defensive check to dsse type
Signed-off-by: Bob Callaway bcallaway@google.com
* be stricter for DSSE, add another defensive check
Signed-off-by: Bob Callaway bcallaway@google.com
Signed-off-by: Bob Callaway bcallaway@google.com
- Loading branch information
Related news
### 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