Skip to content
Heist/ feed
Back to feed
Medium

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

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2023-33199
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 12:02 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 26 May 2023, 22:52 UTC

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.

osv:CVE-2023-33199
Complete source record
{
  "id": "3700244b4a630153cad7fab48cea631c372514f9e6030a9f681b4911073341c5",
  "url": "https://osv.dev/vulnerability/CVE-2023-33199",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "malformed proposed intoto v0.0.2 entries can cause a panic in Rekor",
    "summary": "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.",
    "evidence": "osv:CVE-2023-33199",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2023-33199",
      "aliases": [
        "CVE-2023-33199",
        "GHSA-frqx-jfcm-6jjr",
        "GO-2023-1795"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/sigstore/rekor",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "20a995116b1548b79e62ba0ad9c29800387e8641"
                },
                {
                  "fixed": "140c5add105179e5ffd9e3e114fd1b6b93aebbd4"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:linuxfoundation:rekor:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.2.0"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "range": [
                      {
                        "fixed": "140c5add105179e5ffd9e3e114fd1b6b93aebbd4"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v1.1.1",
            "v1.1.0",
            "v1.0.0",
            "v1.0.0-rc.1",
            "v1.0-rc",
            "v0.12.1",
            "v0.12.0",
            "v0.11.0",
            "v0.10.0",
            "v0.9.1",
            "v0.9.0",
            "v0.8.2",
            "v0.8.1",
            "v0.8.0",
            "v0.7.0",
            "v0.6.0",
            "v0.5.0",
            "v0.4.0",
            "v0.3.0",
            "v0.2.0",
            "v0.1.1",
            "v0.1.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-33199.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:35.303608214Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/33xxx/CVE-2023-33199.json",
        "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"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-617"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/33xxx/CVE-2023-33199.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-33199",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 502289,
  "published_at": "2023-05-26T22:52:15.973+00:00"
}