CVE-2012-5825 Tweepy does not verify SSL Certificate
Tweepy fails to validate SSL certificates, allowing man-in-the-middle attackers to intercept or modify data via spoofed servers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2012-5825?
CVE-2012-5825 is a high-severity vulnerability in n/a, published on 4 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-20
Which versions are affected by CVE-2012-5825?
3 open source packages ship an affected version, including tweepy. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tweepy PyPI | All versions | 2.3.1 |
tweepy PyPI | All versions | 3.0 |
tweepy PyPI | All versions | 3.0 |
Products include Tweepy Tweepy.
How do I fix CVE-2012-5825?
Upgrade tweepy to a fixed version for your release line: 2.3.1 or 3.0.
Is CVE-2012-5825 being exploited?
There is no known exploitation of CVE-2012-5825 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2012-5825, GHSA-pwx5-xg7g-wpc5, PYSEC-2012-17.