OpenBao up to 2.4.1 ACME log file

Summaryinfo

A vulnerability has been found in OpenBao up to 2.4.1 and classified as problematic. This issue affects some unknown processing of the component ACME. Performing a manipulation results in log file. This vulnerability is cataloged as CVE-2025-62513. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in OpenBao up to 2.4.1. This affects an unknown part of the component ACME. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:

OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-62513 since 10/15/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 272073 (Fedora 43 : openbao (2025-0687b2debc)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.4.2 eliminates this vulnerability. Applying the patch cc2c476bac66e1d94776c2629793daec3af625f8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (272073). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• OpenBao

Version

• 2.4.0
• 2.4.1

License

• open-source

Website

• Product: https://github.com/openbao/openbao/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion