Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Rekor's compressed archives can result in OOM conditions

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/sigstore/rekor 1.1.1osv · severity unknownFixed by github.com/sigstore/rekor 1.1.1KEV status unknown

cve-program · CVE-2023-30551

Published

Rekor is an open source software supply chain transparency log. Rekor prior to version 1.1.1 may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. The OOM crash has been patched in Rekor version 1.1.1. There are no known workarounds.

Read the publisher's advisory

euvd · EUVD-2023-1450

Published

Rekor is an open source software supply chain transparency log. Rekor prior to version 1.1.1 may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. The OOM crash has been patched in Rekor version 1.1.1. There are no known workarounds.

Read the publisher's advisory

nvd · CVE-2023-30551

Published

Rekor is an open source software supply chain transparency log. Rekor prior to version 1.1.1 may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. The OOM crash has been patched in Rekor version 1.1.1. There are no known workarounds.

Read the publisher's advisory

osv · GHSA-2h5h-59f5-c5x9

Published

## Summary Two vulnerabilities have been found in Rekor types for archive files JARs and APKs, where Rekor would crash due to out of memory conditions caused by reading archive metadata files into memory without checking their sizes first causing a Denial of Service of Rekor. These vulnerabilities were found through fuzzing with [OSS-Fuzz](https://google.github.io/oss-fuzz/). ## Vulnerability 1: OOM due to large files in META-INF directory of JAR files. ### Summary Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. ### Details As part of verifying a JAR file, Rekor uses the [relic library](http://github.com/sassoftware/relic) to check that the JAR is signed, the signature verifies, and that the hashes in the signed manifest are all valid. This library function reads files within META-INF/ into memory without checking their sizes, resulting in an OOM if the uncompressed file is sufficiently large. Rekor is also not performing any such checks prior to passing the JAR to this library function. ### Patches Users should update to the latest version of Rekor, 1.1.1. ### Workaround There are no workarounds, users should update. ## Vulnerability 2: OOM due to large .SIGN and .PKGINFO files in APK files. ### Summary Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. ### Details When parsing an APK file, Rekor allocates byte slices to read both the .SIGN and .PKGINFO files into memory in order to verify the signature and hashes in the APK. These byte slices are allocated based on the size included in the tar header for each file, with no checks performed on that size. If the size in the header is sufficiently large, either because the uncompressed file is large or the size in the header has been artificially set to a large value, Rekor will crash due to an out of memory panic. ### Patches Users should update to the latest version of Rekor, 1.1.1. ### Workaround There are no workarounds, users should update.

Read the publisher's advisory

osv · GO-2023-1754

Published

Rekor's compressed archives can result in OOM conditions in github.com/sigstore/rekor

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-30551

Published

rekor

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "sigstore",
                    "product": "rekor",
                    "versions": [
                        {
                            "version": "< 1.1.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2023-1450

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 8, 2023, 3:52:42 PM

dateUpdated: Jan 29, 2025, 3:30:31 PM

4 related source bulletins · separate from aliases

RHSA-2023:7198: Red Hat Security Advisory: OpenShift Container Platform 4.15.0 bug fix and security update

CVE-2023-3978 · CVE-2023-26159 · CVE-2023-30551 · CVE-2023-37788 · CVE-2023-39325 · CVE-2023-39326 · CVE-2023-40577 · CVE-2023-44487 · CVE-2023-45142 · CVE-2023-45285 · CVE-2023-47108 · CVE-2023-48795 · CVE-2023-49569

SUSE-SU-2023:2210-1: Security update for rekor

CVE-2023-30551

RHSA-2023:7323: Red Hat Security Advisory: OpenShift Container Platform 4.13.23 bug fix and security update

CVE-2023-30551 · CVE-2023-39325

openSUSE-SU-2024:12919-1: rekor-1.1.1-2.1 on GA media

CVE-2023-30551

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-30551

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-770

Original publisher date fields

published: 2023-05-08T16:15:09.453

lastModified: 2026-06-17T05:55:00.580

1 source CPE criteria · context only
  • cpe:2.3:a:linuxfoundation:rekor:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-2h5h-59f5-c5x9

Published

github.com/sigstore/rekor

Go

SEMVER · introduced 0 → fixed 1.1.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2023-1754

Published

github.com/sigstore/rekor

Go

SEMVER · introduced 0 → fixed 1.1.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current