{"answers":{"affected":"3 open source packages ship an affected version, including sanic. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16762 in the wild and no public exploit code.","fix":"Upgrade sanic to 0.5.1 or later.","what":"CVE-2017-16762 is a high-severity path traversal vulnerability in n/a, published on 10 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16762 and fix it if it is affected.\n\nWhat it is: CVE-2017-16762 is a high-severity path traversal vulnerability in n/a, published on 10 Nov 2017. 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-2017-16762 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sanic (PyPI): affected all versions; fixed in 0.5.1\n- sanic (PyPI): affected all versions; fixed in 0.5.1\n- sanic (PyPI): affected all versions; fixed in 0.5.1\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-2017-16762/ (Markdown: https://insights.sbomify.com/CVE-2017-16762/index.md)","id":"CVE-2017-16762","markdown":"https://insights.sbomify.com/CVE-2017-16762/index.md","name":"CVE-2017-16762","record":{"aliases":["GHSA-mpmf-hr8p-p49g","PYSEC-2017-40"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sanic web framework","requires_auth":"none","summary":"An attacker can read arbitrary files from the server via directory traversal in the Sanic web framework.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sanic","vendor":"sanic_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Sanic before 0.5.1 allows reading arbitrary files with directory traversal, as demonstrated by the /static/..%2f substring.","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":"Sanic arbitrary file read and directory traversal","id":"CVE-2017-16762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":3,"n_references":2,"next":{"headline":"Unsafe deserialization in confire","id":"CVE-2017-16763"},"packages":[{"ecosystem":"PyPI","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"sanic","purl":null,"source":"GHSA-mpmf-hr8p-p49g"},{"ecosystem":"PyPI","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"sanic","purl":"pkg:pypi/sanic","source":"GHSA-mpmf-hr8p-p49g"},{"ecosystem":"PyPI","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"sanic","purl":"pkg:pypi/sanic","source":"PYSEC-2017-40"}],"prev":{"headline":"Open redirect in n/a","id":"CVE-2017-16761"},"products":["n/a"],"published":"2017-11-10","related":[{"cvss_score":8.3,"headline":"Improper Limitation of a Pathname to a Restricted Directory in sanic","id":"CVE-2022-35920","kev_date_added":null,"published":"2022-08-01"}],"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-05","vendors":["n/a"]},"summary":"An attacker can read arbitrary files from the server via directory traversal in the Sanic web framework.","url":"https://insights.sbomify.com/CVE-2017-16762/"}