Security readout for executives and security teams
Plain-English summary
WAL-G could make database backups that were expected to be encrypted but were uploaded in cleartext when a non-libsodium build was used. The main business risk is accidental exposure of sensitive backup contents, especially if cloud backup storage is broadly accessible or retained for long periods.
Executive priority
Treat as high priority if WAL-G protects database backups containing regulated, customer, or operational data. The issue may already have produced cleartext historical backups, so remediation should include storage review, not only software update.
Technical view
CVE-2021-38599 affects WAL-G before 1.1 using non-libsodium builds, including cited official GitHub release binaries. In that condition, WAL-G silently ignored the libsodium encryption key and uploaded backups without encryption. The record provides no CVSS score, CWE, or product CPE detail.
Likely exposure
Exposure is likely limited to environments using WAL-G before 1.1, a non-libsodium build, and libsodium encryption configuration. The highest concern is historical backups created under that combination.
Exploitation context
The source bundle does not show KEV listing or active exploitation. This is not described as remote code execution; the practical risk is that anyone with access to affected backup objects may read data believed to be encrypted.
Researcher notes
The public record is narrow: affected condition, silent key ignore behavior, and cleartext upload. It lacks CVSS, CWE, CPEs, exploit evidence, and detailed vendor advisory text. Avoid broad product claims beyond WAL-G before 1.1 non-libsodium builds.
Mitigation direction
- Upgrade WAL-G to version 1.1 or later where applicable.
- Use a WAL-G build with libsodium support when libsodium encryption is required.
- Review vendor guidance and the referenced fix before changing backup procedures.
- Restrict access to backup storage containing possibly cleartext backups.
- Recreate, encrypt, or retire affected backups after confirming business retention needs.
Validation and detection
- Inventory WAL-G versions and build types used for backup jobs.
- Confirm whether libsodium encryption keys were configured in affected environments.
- Identify backups created by WAL-G before 1.1 non-libsodium builds.
- Verify affected backup objects are not stored as readable cleartext.
- Review the referenced pull request and commit for expected fixed behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-38599 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wal-g/wal-g/pull/1062CVE reference · x_refsource_MISC
- https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.