{"answers":{"affected":"3 open source packages ship an affected version, including tweepy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-5825 in the wild and no public exploit code.","fix":"Upgrade tweepy to a fixed version for your release line: 2.3.1 or 3.0.","what":"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."},"fix_prompt":"Check this codebase for CVE-2012-5825 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2012-5825 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tweepy (PyPI): affected all versions; fixed in 2.3.1\n- tweepy (PyPI): affected all versions; fixed in 3.0\n- tweepy (PyPI): affected all versions; fixed in 3.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2012-5825/ (Markdown: https://insights.sbomify.com/CVE-2012-5825/index.md)","id":"CVE-2012-5825","markdown":"https://insights.sbomify.com/CVE-2012-5825/index.md","name":"CVE-2012-5825","record":{"aliases":["DEBIAN-CVE-2012-5825","GHSA-pwx5-xg7g-wpc5","PYSEC-2012-17"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python Twitter API library","requires_auth":"none","summary":"Tweepy fails to validate SSL certificates, allowing man-in-the-middle attackers to intercept or modify data via spoofed servers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tweepy","vendor":"tweepy"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Tweepy does not verify SSL Certificate","id":"CVE-2012-5825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2012"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2012-5827"},"packages":[{"ecosystem":"PyPI","fixed":["2.3.1"],"introduced":["0"],"last_affected":[],"package":"tweepy","purl":"pkg:pypi/tweepy","source":"PYSEC-2012-17"},{"ecosystem":"PyPI","fixed":["3.0"],"introduced":["0"],"last_affected":[],"package":"tweepy","purl":null,"source":"GHSA-pwx5-xg7g-wpc5"},{"ecosystem":"PyPI","fixed":["3.0"],"introduced":["0"],"last_affected":[],"package":"tweepy","purl":"pkg:pypi/tweepy","source":"GHSA-pwx5-xg7g-wpc5"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2012-5824"},"products":["n/a"],"published":"2012-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Tweepy fails to validate SSL certificates, allowing man-in-the-middle attackers to intercept or modify data via spoofed servers.","url":"https://insights.sbomify.com/CVE-2012-5825/"}