Cleartext backup exposure via ignored encryption keys
Published Aug 12, 2021 · Updated Aug 4, 2024
Cleartext backup exposure in WAL-G before 1.1 allows attackers to read backups uploaded by non-libsodium builds despite configured encryption. In internal/configure_crypter.go, configureLibsodiumCrypter returned a nil crypter without checking WALG_LIBSODIUM_KEY or WALG_LIBSODIUM_KEY_PATH, so backup processing continued unencrypted. The condition requires a build compiled without libsodium and a configured libsodium key; anyone with access to the uploaded backups can read their database contents.
Summary
What happened
Cleartext backup exposure in WAL-G before 1.1 allows attackers to read backups uploaded by non-libsodium builds despite configured encryption. In internal/configure_crypter.go, configureLibsodiumCrypter returned a nil crypter without checking WALG_LIBSODIUM_KEY or WALG_LIBSODIUM_KEY_PATH, so backup processing continued unencrypted. The condition requires a build compiled without libsodium and a configured libsodium key; anyone with access to the uploaded backups can read their database contents.
The record
- CVE
- CVE-2021-38599
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-754, T1530
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo