Skip to content
Fencer Intel
medium 5.9

CVE-2012-3446 json

Apache Libcloud vulnerable to certificate impersonation

published 2012-11-04 14 y ago modified 2026-06-16 4 mo ago also GHSA-prcq-52f8-fp44 , PYSEC-2012-12 , EUVD-2012-0001

cvss
5.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.

Patch / fix

  • pypi apache-libcloud 0.11.1
  • apache libcloud 0.11.0
  • libcloud Debian 14, Debian 13, Debian 12 0.5.0-1.1

debian advisories DEBIAN-CVE-2012-3446

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-3446 updated cvss 5.8

libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • cs.utexas.edu http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi apache-libcloud
<0.11.1
0.11.1

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-185 Incorrect Regular Expression
  • CWE-20 Improper Input Validation

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.