CVE-2012-3458: Weak Encryption
Beaker before 1.6.4, when using PyCrypto to encrypt sessions, uses AES in ECB cipher mode, which might allow remote attackers to obtain portions of sensitive session data via unspecified vectors.
Other sources
It was discovered that python-beaker, a library for web applications, used weak cryptography with its encryption backend. The encryption backend can use one of several backends, including python-crypto. With the default parameters, when python-crypto is used, it will use ECB cipher mode, and any two 16-byte-aligned plaintext blocks with the same contents will be encrypted into the same ciphertext blocks at the corresponding positions. An attacker able to guess the structure of a part of the session data, and influence contents of some data, could use this to check whether other parts of the session have a specific value.
When python-beaker uses other encryption backends, such as pycryptopp, it uses the CTR cipher mode rather than ECB, which does not have this vulnerability.
In Red Hat Enterprise Linux 6, python-beaker does not support or use python-crypto, and is not vulnerable to this flaw.
In current Fedora releases, python-beaker can use both backends, but prefers pycryptopp (and the package Requires it), and is not vulnerable to this flaw.
Statement:
Not vulnerable. This issue did not affect the versions of python-beaker as shipped with Red Hat Enterprise Linux 6 as it did not include support for using python-crypto.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-3458?
CVE-2012-3458 has a moderate severity rating due to the vulnerabilities in session data encryption.
How do I fix CVE-2012-3458?
To fix CVE-2012-3458, upgrade to Beaker version 1.6.4 or later to avoid the weak AES ECB mode.
What specifically is vulnerable in CVE-2012-3458?
CVE-2012-3458 is vulnerable due to the use of AES in ECB mode for session encryption, which can expose sensitive data.
Which versions of Beaker are affected by CVE-2012-3458?
Beaker versions prior to 1.6.4 are affected by CVE-2012-3458.
Can attackers exploit CVE-2012-3458 remotely?
Yes, attackers can exploit CVE-2012-3458 remotely to obtain portions of sensitive session data.