# CVE-2012-2146: Elixir can leak information due to weak use of crypto

> Elixir library uses static IVs in Blowfish CFB mode, allowing attackers to decrypt database contents and access sensitive information.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vfcg-5ggc-3rxx, PYSEC-2012-13, UBUNTU-CVE-2012-2146

## What is CVE-2012-2146?

CVE-2012-2146 is a medium-severity vulnerability in n/a, published on 26 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-310

## Which versions are affected by CVE-2012-2146?

3 open source packages ship an affected version, including elixir and Elixir. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elixir` | PyPI | All versions | None |
| `elixir` | PyPI | All versions to 0.7.1 | None |
| `Elixir` | PyPI | All versions to 0.7.1 | None |

Products: Ematia Elixir.

## How do I fix CVE-2012-2146?

Upgrade to a fixed version.

## Is CVE-2012-2146 being exploited?

There is no known exploitation of CVE-2012-2146 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2146 and fix it if it is affected.

What it is: CVE-2012-2146 is a medium-severity vulnerability in n/a, published on 26 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2146 in the wild and no public exploit code.

Affected packages and fixed versions:
- elixir (PyPI): affected all versions; no fix listed
- elixir (PyPI): affected all versions up to 0.7.1; no fix listed
- Elixir (PyPI): affected all versions up to 0.7.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2146/ (Markdown: https://insights.sbomify.com/CVE-2012-2146/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2146
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2146
- OSV: https://osv.dev/vulnerability/CVE-2012-2146

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2146/
Summaries are generated and may contain mistakes; the official description above is the record.