Skip to content
Fencer Intel
high 7.4

CVE-2012-5825 json

Tweepy does not verify SSL Certificate

published 2012-11-04 14 y ago modified 2026-09-17 53 d ago also GHSA-pwx5-xg7g-wpc5 , PYSEC-2012-17 , EUVD-2012-0031

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

Summary

Tweepy does not verify that 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 an arbitrary valid certificate, related to use of the Python httplib library.

Patch / fix

  • pypi tweepy 2.3.1, 3.0
  • tweepy tweepy 3.0.0
  • tweepy Debian 12 3.1.0-2

debian advisories DEBIAN-CVE-2012-5825

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-5825 updated cvss 4.3

tweepy: Does not verify that the server hostname matches a domain name in the subject's CN or subjectAltName field of the X.509 certificate

  • 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

0.60% chance of exploitation in the next 30 days, higher than 49% 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 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi tweepy
<3.0
<2.3.1
3.0
2.3.1

Classification

Weakness
  • 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.