{"answers":{"affected":"2 open source packages ship an affected version, including com.typesafe.play:play-ws_2.12. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17598 in the wild and no public exploit code.","fix":"Upgrade com.typesafe.play:play-ws_2.12 to 2.6.24 or later.","what":"CVE-2019-17598 is a high-severity vulnerability in n/a, published on 5 Nov 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-17598 and fix it if it is affected.\n\nWhat it is: CVE-2019-17598 is a high-severity vulnerability in n/a, published on 5 Nov 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-17598 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.typesafe.play:play-ws_2.12 (Maven): affected from 2.5.0; fixed in 2.6.24\n- com.typesafe.play:play-ws_2.12 (Maven): affected from 2.5.0; fixed in 2.6.24\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-17598/ (Markdown: https://insights.sbomify.com/CVE-2019-17598/index.md)","id":"CVE-2019-17598","markdown":"https://insights.sbomify.com/CVE-2019-17598/index.md","name":"CVE-2019-17598","record":{"aliases":["GHSA-442g-gcg6-mhm4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Play Framework HTTP client","requires_auth":"none","summary":"Authenticated proxy credentials may be exposed to target hosts when using HTTPS under high load in the Play Framework HTTP client library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23. When configured to make requests using an authenticated HTTP proxy, play-ws may sometimes, typically under high load, when connecting to a target host using https, expose the proxy credentials to the target host.","ecosystems":["Maven"],"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":"Play Framework Inadequate Encryption Strength vulnerability","id":"CVE-2019-17598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17599"},"packages":[{"ecosystem":"Maven","fixed":["2.6.24"],"introduced":["2.5.0"],"last_affected":[],"package":"com.typesafe.play:play-ws_2.12","purl":null,"source":"GHSA-442g-gcg6-mhm4"},{"ecosystem":"Maven","fixed":["2.6.24"],"introduced":["2.5.0"],"last_affected":[],"package":"com.typesafe.play:play-ws_2.12","purl":"pkg:maven/com.typesafe.play/play-ws_2.12","source":"GHSA-442g-gcg6-mhm4"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-17596"},"products":["n/a"],"published":"2019-11-05","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's Assets controller vulnerable to directory traversal","id":"CVE-2018-13864","kev_date_added":null,"published":"2018-07-17"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated proxy credentials may be exposed to target hosts when using HTTPS under high load in the Play Framework HTTP client library.","url":"https://insights.sbomify.com/CVE-2019-17598/"}