https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 03:23:54 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622 certfr-2025-avi-0622 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622 https://cve.radiocsirt.org/vuln/euvd-2026-212523 EUVD-2026-212523 https://cve.radiocsirt.org/vuln/euvd-2026-212523 https://cve.radiocsirt.org/vuln/fkie_cve-2023-30551 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-30551 https://cve.radiocsirt.org/vuln/ghsa-2h5h-59f5-c5x9 <p><strong>Affected:</strong> Go: github.com/sigstore/rekor</p> <p>## 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.</p> <p>These vulnerabilities were found through fuzzing with [OSS-Fuzz](https://google.github.io/oss-fuzz/).</p> <p>## 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.</p> <p>### 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.</p> <p>### Patches Users should update to the latest version of Rekor, 1.1.1.</p> <p>### Workaround There are no workarounds, users should update.</p> <p>## 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.</p> <p>### Details When p…</p> <p><strong>Affected:</strong> Go: github.com/sigstore/rekor</p> <p>## 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.</p> <p>These vulnerabilities were found through fuzzing with [OSS-Fuzz](https://google.github.io/oss-fuzz/).</p> <p>## 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.</p> <p>### 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.</p> <p>### Patches Users should update to the latest version of Rekor, 1.1.1.</p> <p>### Workaround There are no workarounds, users should update.</p> <p>## 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.</p> <p>### Details When p…</p> https://cve.radiocsirt.org/vuln/ghsa-2h5h-59f5-c5x9 https://cve.radiocsirt.org/vuln/gsd-2023-30551 gsd-2023-30551 https://cve.radiocsirt.org/vuln/gsd-2023-30551 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12919-1 <p>rekor-1.1.1-2.1 on GA media</p> <p>rekor-1.1.1-2.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:12919-1 https://cve.radiocsirt.org/vuln/rhsa-2023:7198 <p>golang.org/x/net/html: Cross site scripting follow-redirects: Improper Input Validation due to the improper handling of URLs by the url.parse() rekor: compressed archives can result in OOM conditions goproxy: Denial of service (DoS) via unspecified vectors. golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487) golang: net/http/internal: Denial of Service (DoS) via Resource Consumption via HTTP requests prometheus-alertmanager: UI is vulnerable to stored XSS via the /api/v1/alerts endpoint HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack) opentelemetry: DoS vulnerability in otelhttp golang: cmd/go: Protocol Fallback when fetching modules opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound cardinality metrics ssh: Prefix truncation attack on Binary Packet Protocol (BPP) go-git: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients</p> <p>golang.org/x/net/html: Cross site scripting follow-redirects: Improper Input Validation due to the improper handling of URLs by the url.parse() rekor: compressed archives can result in OOM conditions goproxy: Denial of service (DoS) via unspecified vectors. golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487) golang: net/http/internal: Denial of Service (DoS) via Resource Consumption via HTTP requests prometheus-alertmanager: UI is vulnerable to stored XSS via the /api/v1/alerts endpoint HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack) opentelemetry: DoS vulnerability in otelhttp golang: cmd/go: Protocol Fallback when fetching modules opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound cardinality metrics ssh: Prefix truncation attack on Binary Packet Protocol (BPP) go-git: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients</p> https://cve.radiocsirt.org/vuln/rhsa-2023:7198