{"answers":{"affected":"2 open source packages ship an affected version, including com.typesafe.play:play_2.12. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-13864 in the wild and no public exploit code.","fix":"Upgrade com.typesafe.play:play_2.12 to 2.6.16 or later.","what":"CVE-2018-13864 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-13864 and fix it if it is affected.\n\nWhat it is: CVE-2018-13864 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 2018. 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-2018-13864 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.typesafe.play:play_2.12 (Maven): affected from 2.6.12; fixed in 2.6.16\n- com.typesafe.play:play_2.12 (Maven): affected from 2.6.12; fixed in 2.6.16\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-2018-13864/ (Markdown: https://insights.sbomify.com/CVE-2018-13864/index.md)","id":"CVE-2018-13864","markdown":"https://insights.sbomify.com/CVE-2018-13864/index.md","name":"CVE-2018-13864","record":{"aliases":["GHSA-v4mq-p756-p4f5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Play Framework","requires_auth":"none","summary":"Remote attackers can download arbitrary files from Windows servers running Play Framework via directory traversal in the Assets controller.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"play_framework","vendor":"lightbend"}],"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":"A directory traversal vulnerability has been found in the Assets controller in Play Framework 2.6.12 through 2.6.15 (fixed in 2.6.16) when running on Windows. It allows a remote attacker to download arbitrary files from the target server via specially crafted HTTP requests.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2018-11-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-11-19T09:40:47Z","kind":"github_poc","ref":"https://github.com/tafamace/CVE-2018-13864","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Play Framework's Assets controller vulnerable to directory traversal","id":"CVE-2018-13864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-13865"},"packages":[{"ecosystem":"Maven","fixed":["2.6.16"],"introduced":["2.6.12"],"last_affected":[],"package":"com.typesafe.play:play_2.12","purl":null,"source":"GHSA-v4mq-p756-p4f5"},{"ecosystem":"Maven","fixed":["2.6.16"],"introduced":["2.6.12"],"last_affected":[],"package":"com.typesafe.play:play_2.12","purl":"pkg:maven/com.typesafe.play/play_2.12","source":"GHSA-v4mq-p756-p4f5"}],"prev":{"headline":"js-bson vulnerable to REDoS","id":"CVE-2018-13863"},"products":["n/a"],"published":"2018-07-17","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2014-3630","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":7.5,"headline":"Denial of service binding form from JSON in Play Framework","id":"CVE-2022-31018","kev_date_added":null,"published":"2022-06-02"},{"cvss_score":7.5,"headline":"Data Amplification in Play Framework","id":"CVE-2020-26882","kev_date_added":null,"published":"2020-11-06"},{"cvss_score":7.5,"headline":"Uncontrolled Recursion in Play Framework","id":"CVE-2020-26883","kev_date_added":null,"published":"2020-11-06"},{"cvss_score":7.5,"headline":"Out-of-bounds Write in Play Framework","id":"CVE-2020-27196","kev_date_added":null,"published":"2020-11-06"},{"cvss_score":7.5,"headline":"Play Framework Inadequate Encryption Strength vulnerability","id":"CVE-2019-17598","kev_date_added":null,"published":"2019-11-05"}],"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":"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can download arbitrary files from Windows servers running Play Framework via directory traversal in the Assets controller.","url":"https://insights.sbomify.com/CVE-2018-13864/"}