# 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.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vrmr-f2qh-3hhf

## 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 (Improper Check for Unusual or Exceptional Conditions)

## 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 | Ecosystem | 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: 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38599 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2021-38599 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/wal-g/wal-g (Go): affected all versions; fixed in 1.1
- github.com/wal-g/wal-g (Go): affected all versions; fixed in 1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-38599/ (Markdown: https://insights.sbomify.com/CVE-2021-38599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-38599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-38599
- OSV: https://osv.dev/vulnerability/CVE-2021-38599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-38599/
Summaries are generated and may contain mistakes; the official description above is the record.