In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to insertion of sensitive information into a log file when it attempts to revoke a Vault batch token.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Spring_cloud_config | Vmware | 3.1.0 (including) | 3.1.6 (including) |
| Spring_cloud_config | Vmware | 4.0.0 (including) | 4.0.1 (including) |
| Spring_cloud_vault | Vmware | 3.1.0 (including) | 3.1.2 (including) |
| Spring_cloud_vault | Vmware | 4.0.0 (including) | 4.0.0 (including) |
| Spring_vault | Vmware | 2.3.0 (including) | 2.3.3 (excluding) |
| Spring_vault | Vmware | 3.0.0 (including) | 3.0.2 (excluding) |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: