{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13404 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13404 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13404 is a high-severity vulnerability in Python Python, published on 8 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-13404 and fix it if it is affected.\n\nWhat it is: CVE-2019-13404 is a high-severity vulnerability in Python Python, published on 8 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-13404 in the wild and no public exploit code.\n\nAffected product: Python Python. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2019-13404/ (Markdown: https://insights.sbomify.com/CVE-2019-13404/index.md)","id":"CVE-2019-13404","markdown":"https://insights.sbomify.com/CVE-2019-13404/index.md","name":"CVE-2019-13404","record":{"aliases":["GHSA-vjph-xp4h-fpjw"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python Windows installer","requires_auth":"none","summary":"Local attackers can execute arbitrary code by placing malicious files in the default Python installation directory due to insecure permissions.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"python","vendor":"python"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"}],"description":"The MSI installer for Python through 2.7.16 on Windows defaults to the C:\\Python27 directory, which makes it easier for local users to deploy Trojan horse code. (This also affects old 3.x releases before 3.5.) NOTE: the vendor's position is that it is the user's responsibility to ensure C:\\Python27 access control or choose a different directory, because backwards compatibility requires that C:\\Python27 remain the default for 2.7.x","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privilege escalation in n/a","id":"CVE-2019-13404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"python:python","products":["python:python"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Advan VD-1 allows a remote user to enable Android Debug Bridge without any authentication","id":"CVE-2019-13405"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-13403"},"products":["n/a"],"published":"2019-07-08","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2008-5031","kev_date_added":null,"published":"2008-11-10"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2014-4650","kev_date_added":null,"published":"2020-02-20"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-5636","kev_date_added":null,"published":"2016-09-02"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2007-4559","kev_date_added":null,"published":"2007-08-28"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-17522","kev_date_added":null,"published":"2017-12-14"},{"cvss_score":8.7,"headline":"Incremental HTMLParser feed() allows CPU-exhaustion DoS via repeated unterminated markup declarations","id":"CVE-2026-15308","kev_date_added":null,"published":"2026-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"Local attackers can execute arbitrary code by placing malicious files in the default Python installation directory due to insecure permissions.","url":"https://insights.sbomify.com/CVE-2019-13404/"}