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."
Published: 2021-08-12
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2021-2117 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."
Github GHSA Github GHSA GHSA-vrmr-f2qh-3hhf Improper use of cryptographic key in wal-g
History

Wed, 16 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.00211}

epss

{'score': 0.0017}


Subscriptions

Wal-g Project Wal-g
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-04T01:44:23.479Z

Reserved: 2021-08-12T00:00:00.000Z

Link: CVE-2021-38599

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2021-08-12T16:15:10.533

Modified: 2024-11-21T06:17:38.643

Link: CVE-2021-38599

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses