# 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.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 4 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5825, GHSA-pwx5-xg7g-wpc5, PYSEC-2012-17

## 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 (Improper Input Validation)

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

3 open source packages ship an affected version, including tweepy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tweepy` | PyPI | All versions | 2.3.1 |
| `tweepy` | PyPI | All versions | 3.0 |
| `tweepy` | PyPI | All versions | 3.0 |

Products: 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.

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: There is no known exploitation of CVE-2012-5825 in the wild and no public exploit code.

Affected packages and fixed versions:
- tweepy (PyPI): affected all versions; fixed in 2.3.1
- tweepy (PyPI): affected all versions; fixed in 3.0
- tweepy (PyPI): affected all versions; fixed in 3.0

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-5825/ (Markdown: https://insights.sbomify.com/CVE-2012-5825/index.md)
```

## Sources

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

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