Rekor's compressed archives can result in OOM conditions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sigstore | rekor | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.13 | |||
| openshift4/ose-docker-builder:v4.13.0-202311091630.p0.g0155fb1.assembly.stream | cpe:/a:redhat:openshift:4.13::el8 | RHSA-2023:7323 | 2023-11-21T00:00:00Z |
| Red Hat OpenShift Container Platform 4.15 | |||
| openshift4/ose-openshift-controller-manager-rhel9:v4.15.0-202402040308.p0.g87d2511.assembly.stream | cpe:/a:redhat:openshift:4.15::el9 | RHSA-2023:7198 | 2024-02-27T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-1450 | 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. |
Github GHSA |
GHSA-2h5h-59f5-c5x9 | Rekor's compressed archives can result in OOM conditions |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.050% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Allocation of Resources Without Limits or Throttling