{"answers":{"affected":"3 open source packages ship an affected version, including libtaxii. It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-27197 in the wild and no public exploit code.","fix":"Upgrade libtaxii to 1.1.118 or later.","what":"CVE-2020-27197 is a critical server-side request forgery vulnerability in n/a, published on 17 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27197 and fix it if it is affected.\n\nWhat it is: CVE-2020-27197 is a critical server-side request forgery vulnerability in n/a, published on 17 Oct 2020. 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-2020-27197 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libtaxii (PyPI): affected all versions; fixed in 1.1.118\n- libtaxii (PyPI): affected all versions; fixed in 1.1.118\n- libtaxii (PyPI): affected all versions; fixed in 1.1.118\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-2020-27197/ (Markdown: https://insights.sbomify.com/CVE-2020-27197/index.md)","id":"CVE-2020-27197","markdown":"https://insights.sbomify.com/CVE-2020-27197/index.md","name":"CVE-2020-27197","record":{"aliases":["GHSA-836c-xg97-8p4h","PYSEC-2020-59"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TAXII Python library","requires_auth":"none","summary":"An attacker can trigger Server-Side Request Forgery in the libtaxii library by manipulating URL parsing, bypassing network restrictions.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opentaxii","vendor":"eclecticiq"},{"product":"libtaxii","vendor":"libtaxii_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"TAXII libtaxii through 1.1.117, as used in EclecticIQ OpenTAXII through 0.2.0 and other products, allows SSRF via an initial http:// substring to the parse method, even when the no_network setting is used for the XML parser. NOTE: the vendor points out that the parse method \"wraps the lxml library\" and that this may be an issue to \"raise ... to the lxml group.","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":"libtaxii Server-Side Request Forgery vulnerability","id":"CVE-2020-27197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":3,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-27199"},"packages":[{"ecosystem":"PyPI","fixed":["1.1.118"],"introduced":["0"],"last_affected":[],"package":"libtaxii","purl":null,"source":"GHSA-836c-xg97-8p4h"},{"ecosystem":"PyPI","fixed":["1.1.118"],"introduced":["0"],"last_affected":[],"package":"libtaxii","purl":"pkg:pypi/libtaxii","source":"GHSA-836c-xg97-8p4h"},{"ecosystem":"PyPI","fixed":["1.1.118"],"introduced":["0"],"last_affected":[],"package":"libtaxii","purl":"pkg:pypi/libtaxii","source":"PYSEC-2020-59"}],"prev":{"headline":"Out-of-bounds Write in Play Framework","id":"CVE-2020-27196"},"products":["n/a"],"published":"2020-10-17","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-04","vendors":["n/a"]},"summary":"An attacker can trigger Server-Side Request Forgery in the libtaxii library by manipulating URL parsing, bypassing network restrictions.","url":"https://insights.sbomify.com/CVE-2020-27197/"}