{"answers":{"affected":"2 open source packages ship an affected version, including io.ratpack:ratpack-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17513 in the wild and no public exploit code.","fix":"Upgrade io.ratpack:ratpack-core to 1.7.5 or later.","what":"CVE-2019-17513 is a high-severity vulnerability in n/a, published on 18 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-17513 and fix it if it is affected.\n\nWhat it is: CVE-2019-17513 is a high-severity vulnerability in n/a, published on 18 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-17513 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.ratpack:ratpack-core (Maven): affected all versions; fixed in 1.7.5\n- io.ratpack:ratpack-core (Maven): affected all versions; fixed in 1.7.5\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-17513/ (Markdown: https://insights.sbomify.com/CVE-2019-17513/index.md)","id":"CVE-2019-17513","markdown":"https://insights.sbomify.com/CVE-2019-17513/index.md","name":"CVE-2019-17513","record":{"aliases":["GHSA-mvqp-q37c-wf9j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ratpack Java framework","requires_auth":"none","summary":"Attackers can perform HTTP Response Splitting by injecting control characters into headers constructed from untrusted data in the Ratpack framework.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ratpack","vendor":"ratpack_project"}],"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-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"An issue was discovered in Ratpack before 1.7.5. Due to a misuse of the Netty library class DefaultHttpHeaders, there is no validation that headers lack HTTP control characters. Thus, if untrusted data is used to construct HTTP headers with Ratpack, HTTP Response Splitting can occur.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2024-05-31","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-05-31T20:26:56Z","kind":"github_poc","ref":"https://github.com/epicosy/Ratpack-1","stars":0,"title":"ratpack with CVE-2019-17513"}],"tier":"poc_unverified"},"has_fix":true,"headline":"io.ratpack:ratpack-core vulnerable to Improper Neutralization of Special Elements in Output ('Injection')","id":"CVE-2019-17513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2019"},"n_packages":2,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-17514"},"packages":[{"ecosystem":"Maven","fixed":["1.7.5"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-core","purl":null,"source":"GHSA-mvqp-q37c-wf9j"},{"ecosystem":"Maven","fixed":["1.7.5"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-core","purl":"pkg:maven/io.ratpack/ratpack-core","source":"GHSA-mvqp-q37c-wf9j"}],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-17512"},"products":["n/a"],"published":"2019-10-18","related":[{"cvss_score":9.9,"headline":"Remote Code Execution Vulnerability in Session Storage","id":"CVE-2021-29485","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":7,"headline":"Cached redirect poisoning via X-Forwarded-Host header","id":"CVE-2021-29479","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":6.5,"headline":"Client side sessions should not allow unencrypted storage","id":"CVE-2021-29481","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":4.4,"headline":"Default client side session signing key is highly predictable","id":"CVE-2021-29480","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":3.7,"headline":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack","id":"CVE-2019-11808","kev_date_added":null,"published":"2019-05-07"}],"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":"Attackers can perform HTTP Response Splitting by injecting control characters into headers constructed from untrusted data in the Ratpack framework.","url":"https://insights.sbomify.com/CVE-2019-17513/"}