CVE-2023-33199

malformed proposed intoto v0.0.2 entries can cause a panic in Rekor

Description

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.

Category

5.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.11%
Vendor Advisory github.com
Affected: sigstore rekor
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2023-33199?
CVE-2023-33199 has been scored as a medium severity vulnerability.
How to fix CVE-2023-33199?
To fix CVE-2023-33199, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-33199 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-33199 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-33199?
CVE-2023-33199 affects sigstore rekor.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.