First published: Fri Dec 13 2013(Updated: )
Percona XtraBackup before 2.1.6 uses a constant string for the initialization vector (IV), which makes it easier for local users to defeat cryptographic protection mechanisms and conduct plaintext attacks.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Percona XtraBackup | <=2.1.5 | |
Percona XtraBackup | =2.1.0-alpha1 | |
Percona XtraBackup | =2.1.0-beta1 | |
Percona XtraBackup | =2.1.0-rc1 | |
Percona XtraBackup | =2.1.1 | |
Percona XtraBackup | =2.1.2 | |
Percona XtraBackup | =2.1.3 | |
Percona XtraBackup | =2.1.4 | |
SUSE Linux | =13.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-6394 is rated as a moderate severity vulnerability due to its potential to weaken cryptographic protections.
To fix CVE-2013-6394, upgrade to Percona XtraBackup version 2.1.6 or later.
CVE-2013-6394 affects all versions of Percona XtraBackup prior to 2.1.6 as well as specific alpha, beta, and release candidate versions.
CVE-2013-6394 involves cryptographic vulnerabilities due to the use of a constant initialization vector.
Yes, local users can exploit CVE-2013-6394 to conduct plaintext attacks against encrypted data.