First published: Thu Mar 23 2023(Updated: )
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.
Credit: security@vmware.com
Affected Software | Affected Version | How to fix |
---|---|---|
Vmware Spring Cloud Config | >=3.1.0<=3.1.6 | |
Vmware Spring Cloud Config | >=4.0.0<=4.0.1 | |
Vmware Spring Cloud Vault | >=3.1.0<=3.1.2 | |
Vmware Spring Cloud Vault | =4.0.0 | |
Vmware Spring Vault | >=2.3.0<2.3.3 | |
Vmware Spring Vault | >=3.0.0<3.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-20859 is considered a high severity vulnerability because it allows for the insertion of sensitive information into log files, posing a potential data leakage risk.
To fix CVE-2023-20859, upgrade Spring Vault to version 3.0.2 or 2.3.3 or later versions.
CVE-2023-20859 affects Spring Vault versions 3.0.x prior to 3.0.2, 2.3.x prior to 2.3.3, and older versions.
Applications using the affected versions of Spring Vault are impacted by CVE-2023-20859.
There are no documented workarounds for CVE-2023-20859; updating to a patched version is the recommended mitigation.