CVE-2012-3458: Weak Encryption

Published Apr 2, 2012
·
Updated

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

2 affected componentsFixes available
pip/beaker<1.6.4
1.6.4
Python beaker<=1.6.4

Event History

Apr 2, 2012
Data Sourced
via Red Hat·10:28 PM
DescriptionSeverityAffected Software
Sep 15, 2012
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·05:22 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-3458?

CVE-2012-3458 has a moderate severity rating due to the vulnerabilities in session data encryption.

2

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.

3

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.

4

Which versions of Beaker are affected by CVE-2012-3458?

Beaker versions prior to 1.6.4 are affected by CVE-2012-3458.

5

Can attackers exploit CVE-2012-3458 remotely?

Yes, attackers can exploit CVE-2012-3458 remotely to obtain portions of sensitive session data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203