CyberRota Analysis
AI-GeneratedThe vulnerability affects the hashi-vault-js Node.js module, which improperly handles error responses from the HashiCorp Vault API, potentially exposing sensitive information such as the X-Vault-Token and request body in plaintext logs. This can lead to unauthorized access to the Vault instance if an attacker gains access to these logs. Organizations using versions prior to 0.5.2 should prioritize upgrading to mitigate the risk of credential exposure.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
hashi-vault-js is a Node.js module for interacting with the HashiCorp Vault API. Prior to 0.5.2, every API method in src/Vault.js passes failed requests through parseAxiosError(), which rethrows the raw AxiosError while retaining AxiosError.config and the equivalent response configuration. These objects can contain the X-Vault-Token request header and err.config.data request body, including submitted passwords or secret values. When a consuming application records the caught exception through console logging, structured loggers, monitoring, crash reporting, or an application performance monitoring service, the live Vault token and request secrets can be stored in plaintext and exposed to anyone with access to that output. A stolen token can permit unauthorized access to the Vault instance under the token's policies. This issue is fixed in version 0.5.2.