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."
{
"extracted_events": [
{
"cpe": "cpe:2.3:a:wal-g_project:wal-g:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.1"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "cadf598e1c2a345915a21a44518c5a4d5401e2e3"
}
],
"source": "REFERENCES_COMMIT"
}
]
}