Reachable Assertion Affecting rekor package, versions <1.2.1-150400.4.12.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.11% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-REKOR-5710998
  • published16 Jun 2023
  • disclosed15 Jun 2023

Introduced: 15 Jun 2023

CVE-2023-33199  (opens in a new tab)
CWE-617  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 rekor to version 1.2.1-150400.4.12.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rekor package and not the rekor package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

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 Base Scores

version 3.1