{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17514 in the wild and no public exploit code.","fix":"Apply a workaround.","what":"CVE-2019-17514 is a high-severity vulnerability in Python Python, published on 12 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17514 and fix it if it is affected.\n\nWhat it is: CVE-2019-17514 is a high-severity vulnerability in Python Python, published on 12 Oct 2019. 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-2019-17514 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-17514/ (Markdown: https://insights.sbomify.com/CVE-2019-17514/index.md)","id":"CVE-2019-17514","markdown":"https://insights.sbomify.com/CVE-2019-17514/index.md","name":"CVE-2019-17514","record":{"aliases":["GHSA-pgrc-mvjg-qfr7","UBUNTU-CVE-2019-17514"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Python standard library","requires_auth":"none","summary":"Misleading documentation regarding glob sorting led to non-deterministic behavior in dependent applications, requiring explicit sorting in affected scripts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"python","vendor":"python"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"}],"description":"library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated \"finds all the pathnames matching a specified pattern according to the rules used by the Unix shell,\" one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2019-17514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"python:python","products":["python:python"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":14,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17515"},"packages":[],"prev":{"headline":"io.ratpack:ratpack-core vulnerable to Improper Neutralization of Special Elements in Output ('Injection')","id":"CVE-2019-17513"},"products":["n/a"],"published":"2019-10-12","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"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-13404","kev_date_added":null,"published":"2019-07-08"}],"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-05","vendors":["n/a"]},"summary":"Misleading documentation regarding glob sorting led to non-deterministic behavior in dependent applications, requiring explicit sorting in affected scripts.","url":"https://insights.sbomify.com/CVE-2019-17514/"}