CVE-2012-2146: High severity elixir vulnerability
Elixir 0.8.0 uses Blowfish in CFB mode without constructing a unique initialization vector (IV), which makes it easier for context-dependent users to obtain sensitive information and decrypt the database.
Other sources
Elixir prior to and including 0.7.1 uses Blowfish in CFB mode without constructing a unique initialization vector (IV), which makes it easier for context-dependent users to obtain sensitive information and decrypt the database. A patch has been attached to the initial advisory to mitigate this vulnerability.
— GitHub
It was reported that python-elixir, a library for ORM mapping on top of SQLAlchemy with support for encrypting data stored in a database, suffers from weak use of cryptography. It uses Blowfish in CFB mode, which has an additional parameter (IV), which is not specified and thus defaults to zero. CFB mode is only secure if the the IV is unpredictable and different for every message. Because of this, and because the encryption key is shared for each database table (fields and rows), the same plaintext prefix is always encrypted to an identical and corresponding ciphertext prefix. As a result, an attacker with access to the database could figure out the plaintext values of encrypted text.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-2146?
CVE-2012-2146 is considered a high severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2012-2146?
To fix CVE-2012-2146, upgrade Elixir to version 0.8.1 or later which addresses the vulnerability.
What is affected by CVE-2012-2146?
CVE-2012-2146 affects Elixir versions up to and including 0.8.0 and 0.7.1.
What kind of vulnerability is CVE-2012-2146?
CVE-2012-2146 is a cryptographic vulnerability related to the use of Blowfish in CFB mode without a unique initialization vector.
Who should be concerned about CVE-2012-2146?
Developers and organizations using affected versions of Elixir should be concerned about CVE-2012-2146 due to its impact on data security.