CVE-2021-38599 Improper use of cryptographic key in wal-g
WAL-G silently uploads unencrypted backups when using non-libsodium builds, exposing sensitive data to attackers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-38599?
CVE-2021-38599 is a high-severity vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to encrypt all file activity."
Weakness: CWE-754
Which versions are affected by CVE-2021-38599?
2 open source packages ship an affected version, including github.com/wal-g/wal-g. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/wal-g/wal-g Go | All versions | 1.1 |
github.com/wal-g/wal-g Go | All versions | 1.1 |
Products include Wal-G Project Wal-G.
How do I fix CVE-2021-38599?
Upgrade github.com/wal-g/wal-g to 1.1 or later.
Is CVE-2021-38599 being exploited?
There is no known exploitation of CVE-2021-38599 in the wild and no public exploit code.
Sources
Also known as GHSA-vrmr-f2qh-3hhf.