Skip to content
Fencer Intel
high 7.5

CVE-2012-2146 json

Elixir can leak information due to weak use of crypto

published 2012-08-26 14 y ago modified 2026-06-16 4 mo ago also GHSA-vfcg-5ggc-3rxx , PYSEC-2012-13 , EUVD-2012-0007

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

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.

Patch / fix

  • elixir Ubuntu 14.04 LTS 0.7.1-4build0.14.04.1
  • elixir Ubuntu 16.04 LTS 0.7.1-4build0.16.04.1

ubuntu advisories UBUNTU-CVE-2012-2146

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2146 updated cvss 4.9

python-elixir: weak use of crypto can leak information

  • Red Hat Enterprise Linux 6 python-elixir
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi elixir
<=0.7.1
all versions
no fix listed

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.