cve.bz

CVE-2023-33199 linuxfoundation rekor: Reachable Assertion

5.3 mediumEPSS 0.7%Fix available

Medium (5.3) in linuxfoundation rekor. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/sigstore/rekor 1.2.0.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-01-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-33199 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-33199?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-33199?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-33199 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:rekorbefore 1.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-frqx-jfcm-6jjrGogithub.com/sigstore/rekor<1.2.01.2.0
GO-2023-1795Gogithub.com/sigstore/rekor<1.2.01.2.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Basesystem 15 SP4, Linux Enterprise Module for Basesystem 15 SP5rekor1.2.1-150400.4.12.1SUSE-SU-2023:2515-1
openSUSELeap 15.4, Leap 15.5rekor1.2.1-150400.4.12.1SUSE-SU-2023:2515-1
openSUSETumbleweedrekor1.2.1-1.1openSUSE-SU-2024:12965-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

References

Check your stackJSON