CVE-2023-33199
There are no known workarounds for this vulnerability.
Does this matter?
Lower severity and a low EPSS score (0.67%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- 0.67% probability · 50th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-617
- Affected
- linuxfoundation/rekor
- Source
- security-advisories@github.com
References
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4Patch
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjrVendor Advisory
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4Patch
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjrVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.