https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:11:17 +0000 https://cve.radiocsirt.org/vuln/bit-openbao-2025-59043 <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. In OpenBao versions prior to 2.4.1, JSON objects after decoding may use significantly more memory than their serialized version. It is possible to craft a JSON payload to maximize the factor between serialized memory usage and deserialized memory usage, similar to a zip bomb, with factors reaching approximately 35. This can be used to circumvent the max_request_size configuration parameter which is intended to protect against denial of service attacks. The request body is parsed into a map very early in the request handling chain before authentication, which means an unauthenticated attacker can send a specifically crafted JSON object and cause an out-of-memory crash. Additionally, for requests with large numbers of strings, the audit subsystem can consume large quantities of CPU. The vulnerability is fixed in version 2.4.1.</p> <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. In OpenBao versions prior to 2.4.1, JSON objects after decoding may use significantly more memory than their serialized version. It is possible to craft a JSON payload to maximize the factor between serialized memory usage and deserialized memory usage, similar to a zip bomb, with factors reaching approximately 35. This can be used to circumvent the max_request_size configuration parameter which is intended to protect against denial of service attacks. The request body is parsed into a map very early in the request handling chain before authentication, which means an unauthenticated attacker can send a specifically crafted JSON object and cause an out-of-memory crash. Additionally, for requests with large numbers of strings, the audit subsystem can consume large quantities of CPU. The vulnerability is fixed in version 2.4.1.</p> https://cve.radiocsirt.org/vuln/bit-openbao-2025-59043 https://cve.radiocsirt.org/vuln/cnvd-2025-24756 cnvd-2025-24756 https://cve.radiocsirt.org/vuln/cnvd-2025-24756 https://cve.radiocsirt.org/vuln/euvd-2026-255353 EUVD-2026-255353 https://cve.radiocsirt.org/vuln/euvd-2026-255353 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59043 <p>OpenBao is an open source identity-based secrets management system. In OpenBao versions prior to 2.4.1, JSON objects after decoding may use significantly more memory than their serialized version. It is possible to craft a JSON payload to maximize the factor between serialized memory usage and deserialized memory usage, similar to a zip bomb, with factors reaching approximately 35. This can be used to circumvent the max_request_size configuration parameter which is intended to protect against denial of service attacks. The request body is parsed into a map very early in the request handling chain before authentication, which means an unauthenticated attacker can send a specifically crafted JSON object and cause an out-of-memory crash. Additionally, for requests with large numbers of strings, the audit subsystem can consume large quantities of CPU. The vulnerability is fixed in version 2.4.1.</p> <p>OpenBao is an open source identity-based secrets management system. In OpenBao versions prior to 2.4.1, JSON objects after decoding may use significantly more memory than their serialized version. It is possible to craft a JSON payload to maximize the factor between serialized memory usage and deserialized memory usage, similar to a zip bomb, with factors reaching approximately 35. This can be used to circumvent the max_request_size configuration parameter which is intended to protect against denial of service attacks. The request body is parsed into a map very early in the request handling chain before authentication, which means an unauthenticated attacker can send a specifically crafted JSON object and cause an out-of-memory crash. Additionally, for requests with large numbers of strings, the audit subsystem can consume large quantities of CPU. The vulnerability is fixed in version 2.4.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59043 https://cve.radiocsirt.org/vuln/ghsa-g46h-2rq9-gw5m <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Summary</p> <p>JSON objects after decoding might use more memory than their serialized version. It is possible to tune a JSON to maximize the factor between serialized memory usage and deserialized memory usage (similar to a zip bomb). While reproducing the issue, we could reach a factor of about 35. This can be used to circumvent the [`max_request_size` (https://openbao.org/docs/configuration/listener/tcp/) configuration parameter, which is meant to protect against Denial of Service attacks, and also makes Denial of Service attacks easier in general, as the attacker needs much less resources.</p> <p>### Details</p> <p>The request body is parsed into a `map[string]interface{}` https://github.com/openbao/openbao/blob/788536bd3e10818a7b4fb00aac6affc23388e5a9/http/logical.go#L50 very early in the request handling chain (before authentication), which means an attacker can send a specifically crafted JSON object and cause an OOM crash. Additionally, for simpler requests with large numbers of strings, the audit subsystem can consume large quantities of CPU.</p> <p>To remediate, set `max_request_json_memory` and `max_request_json_strings`.</p> <p>### Impact</p> <p>- Unauthenticated Denial of Service</p> <p>### Resources</p> <p>This issue was disclosed directly to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393 - https://nvd.nist.gov/vuln/detail/CVE-2025-6203</p> <p>HashiCorp attributes the problem to the a…</p> <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Summary</p> <p>JSON objects after decoding might use more memory than their serialized version. It is possible to tune a JSON to maximize the factor between serialized memory usage and deserialized memory usage (similar to a zip bomb). While reproducing the issue, we could reach a factor of about 35. This can be used to circumvent the [`max_request_size` (https://openbao.org/docs/configuration/listener/tcp/) configuration parameter, which is meant to protect against Denial of Service attacks, and also makes Denial of Service attacks easier in general, as the attacker needs much less resources.</p> <p>### Details</p> <p>The request body is parsed into a `map[string]interface{}` https://github.com/openbao/openbao/blob/788536bd3e10818a7b4fb00aac6affc23388e5a9/http/logical.go#L50 very early in the request handling chain (before authentication), which means an attacker can send a specifically crafted JSON object and cause an OOM crash. Additionally, for simpler requests with large numbers of strings, the audit subsystem can consume large quantities of CPU.</p> <p>To remediate, set `max_request_json_memory` and `max_request_json_strings`.</p> <p>### Impact</p> <p>- Unauthenticated Denial of Service</p> <p>### Resources</p> <p>This issue was disclosed directly to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393 - https://nvd.nist.gov/vuln/detail/CVE-2025-6203</p> <p>HashiCorp attributes the problem to the a…</p> https://cve.radiocsirt.org/vuln/ghsa-g46h-2rq9-gw5m https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1 <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391 <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391