malformed proposed intoto v0.0.2 entries can cause a panic in Rekor
cve-program · CVE-2023-33199
PublishedRekor'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.
Read the publisher's advisoryeuvd · EUVD-2023-1532
PublishedRekor'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.
Read the publisher's advisorynvd · CVE-2023-33199
PublishedRekor'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.
Read the publisher's advisoryosv · GHSA-frqx-jfcm-6jjr
Published### 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
Read the publisher's advisoryosv · GO-2023-1795
Publishedmalformed proposed intoto entries can cause a panic in github.com/sigstore/rekor
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-33199 · CVE overview and exploitation status
cve-program · CVE-2023-33199
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4
euvd · EUVD-2023-1532
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4
nvd · CVE-2023-33199
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr
osv · GHSA-frqx-jfcm-6jjr
- https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr
- https://nvd.nist.gov/vuln/detail/CVE-2023-33199
- https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4
- https://github.com/sigstore/rekor
osv · GO-2023-1795
Related changes
Linked by CVE identifierNo related changes are available here.