CVE-2021-38599

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

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.21%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/wal-g/wal-g/pull/1062 third party advisory patch
https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2021-38599?
CVE-2021-38599 has been scored as a high severity vulnerability.
How to fix CVE-2021-38599?
To fix CVE-2021-38599, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2021-38599 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2021-38599 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.