{"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-10770 in the wild and no public exploit code.","fix":"Upgrade io.ratpack:ratpack-core to 1.7.6 or later.","what":"CVE-2019-10770 is a medium-severity cross-site scripting vulnerability in io.ratpack:ratpack-core, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-10770 and fix it if it is affected.\n\nWhat it is: CVE-2019-10770 is a medium-severity cross-site scripting vulnerability in io.ratpack:ratpack-core, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-10770 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.6\n- io.ratpack:ratpack-core (Maven): affected all versions; fixed in 1.7.6\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-10770/ (Markdown: https://insights.sbomify.com/CVE-2019-10770/index.md)","id":"CVE-2019-10770","markdown":"https://insights.sbomify.com/CVE-2019-10770/index.md","name":"CVE-2019-10770","record":{"aliases":["GHSA-r2wf-q3x4-hrv9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Java web framework","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via XSS in Ratpack's development mode error handler if untrusted data is present in exception messages.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"ratpack","vendor":"ratpack"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"All versions of io.ratpack:ratpack-core from 0.9.10 inclusive and before 1.7.6 are vulnerable to Cross-site Scripting (XSS). This affects the development mode error handler when an exception message contains untrusted data. Note the production mode error handler is not vulnerable - so for this to be utilized in production it would require users to not disable development mode.","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":"Default development error handler in Ratpack is vulnerable to HTML content injection (XSS)","id":"CVE-2019-10770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-Site Scripting in iobroker.web","id":"CVE-2019-10771"},"packages":[{"ecosystem":"Maven","fixed":["1.7.6"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-core","purl":null,"source":"GHSA-r2wf-q3x4-hrv9"},{"ecosystem":"Maven","fixed":["1.7.6"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-core","purl":"pkg:maven/io.ratpack/ratpack-core","source":"GHSA-r2wf-q3x4-hrv9"}],"prev":{"headline":"Sandbox Breakout / Arbitrary Code Execution in safer-eval","id":"CVE-2019-10769"},"products":["io.ratpack:ratpack-core"],"published":"2020-01-28","related":[],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts via XSS in Ratpack's development mode error handler if untrusted data is present in exception messages.","url":"https://insights.sbomify.com/CVE-2019-10770/"}