https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 14:15:16 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-11280 bdu:2025-11280 https://cve.radiocsirt.org/vuln/bdu:2025-11280 https://cve.radiocsirt.org/vuln/bit-openbao-2025-55000 <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library. To work around, ensure that all codes are first normalized before submitting to the OpenBao endpoint. TOTP code verification is a privileged action; only trusted systems should be verifying codes.</p> <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library. To work around, ensure that all codes are first normalized before submitting to the OpenBao endpoint. TOTP code verification is a privileged action; only trusted systems should be verifying codes.</p> https://cve.radiocsirt.org/vuln/bit-openbao-2025-55000 https://cve.radiocsirt.org/vuln/cnvd-2025-18607 cnvd-2025-18607 https://cve.radiocsirt.org/vuln/cnvd-2025-18607 https://cve.radiocsirt.org/vuln/euvd-2026-249399 EUVD-2026-249399 https://cve.radiocsirt.org/vuln/euvd-2026-249399 https://cve.radiocsirt.org/vuln/fkie_cve-2025-55000 <p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library. To work around, ensure that all codes are first normalized before submitting to the OpenBao endpoint. TOTP code verification is a privileged action; only trusted systems should be verifying codes.</p> <p>OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library. To work around, ensure that all codes are first normalized before submitting to the OpenBao endpoint. TOTP code verification is a privileged action; only trusted systems should be verifying codes.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-55000 https://cve.radiocsirt.org/vuln/ghsa-f7c3-mhj2-9pvg <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library.</p> <p>### Patches</p> <p>OpenBao v2.3.2 will patch this issue.</p> <p>In patching, codes which were not normalized (strictly N numeric digits) will now be rejected. This is a potentially breaking change.</p> <p>### Workarounds</p> <p>TOTP code verification is a privileged action; only trusted systems should be verifying codes. Ensure that all codes are first normalized before submitting to the OpenBao endpoint.</p> <p>### References</p> <p>This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- https://discuss.hashicorp.com/t/hcsec-2025-17-vault-totp-secrets-engine-code-reuse/76036 - https://nvd.nist.gov/vuln/detail/CVE-2025-6014</p> <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao&#39;s TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library.</p> <p>### Patches</p> <p>OpenBao v2.3.2 will patch this issue.</p> <p>In patching, codes which were not normalized (strictly N numeric digits) will now be rejected. This is a potentially breaking change.</p> <p>### Workarounds</p> <p>TOTP code verification is a privileged action; only trusted systems should be verifying codes. Ensure that all codes are first normalized before submitting to the OpenBao endpoint.</p> <p>### References</p> <p>This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- https://discuss.hashicorp.com/t/hcsec-2025-17-vault-totp-secrets-engine-code-reuse/76036 - https://nvd.nist.gov/vuln/detail/CVE-2025-6014</p> https://cve.radiocsirt.org/vuln/ghsa-f7c3-mhj2-9pvg https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1855 <p>Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um beliebigen Code auszuführen, Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.</p> <p>Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um beliebigen Code auszuführen, Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1855