{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17198 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17198 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17198 is a critical server-side request forgery vulnerability in Apache Roller, published on 28 May 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-2018-17198 and fix it if it is affected.\n\nWhat it is: CVE-2018-17198 is a critical server-side request forgery vulnerability in Apache Roller, published on 28 May 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-2018-17198 in the wild and no public exploit code.\n\nAffected product: Apache Roller. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-17198/ (Markdown: https://insights.sbomify.com/CVE-2018-17198/index.md)","id":"CVE-2018-17198","markdown":"https://insights.sbomify.com/CVE-2018-17198/index.md","name":"CVE-2018-17198","record":{"aliases":["GHSA-38f5-5m8x-c6h5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Roller blog","requires_auth":"none","summary":"Attackers can exploit SSRF and file enumeration via XML-RPC interface, even if disabled in UI, by leveraging Java SAX parser external entity support.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"roller","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Server-side Request Forgery (SSRF) and File Enumeration vulnerability in Apache Roller 5.2.1, 5.2.0 and earlier unsupported versions relies on Java SAX Parser to implement its XML-RPC interface and by default that parser supports external entities in XML DOCTYPE, which opens Roller up to SSRF / File Enumeration vulnerability. Note that this vulnerability exists even if Roller XML-RPC interface is disable via the Roller web admin UI. Mitigation: There are a couple of ways you can fix this vulnerability: 1) Upgrade to the latest version of Roller, which is now 5.2.2 2) Or, edit the Roller web.xml file and comment out the XML-RPC Servlet mapping as shown below: \u003c!-- \u003cservlet-mapping\u003e \u003cservlet-name\u003eXmlRpcServlet\u003c/servlet-name\u003e \u003curl-pattern\u003e/roller-services/xmlrpc\u003c/url-pattern\u003e \u003c/servlet-mapping\u003e --\u003e","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in Apache Roller","id":"CVE-2018-17198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Apache HTTP Server","id":"CVE-2018-17199"},"packages":[],"prev":{"headline":"Apache Tika Denial of Service due to Infinite Loop in Tika's SQLite3Parser","id":"CVE-2018-17197"},"products":["Apache Roller"],"published":"2019-05-28","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2014-0030","kev_date_added":null,"published":"2017-10-09"},{"cvss_score":7.5,"headline":"regex injection leading to DoS","id":"CVE-2021-33580","kev_date_added":null,"published":"2021-08-18"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2015-0249","kev_date_added":null,"published":"2017-07-14"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2013-4212","kev_date_added":null,"published":"2013-12-07"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2012-2380","kev_date_added":null,"published":"2012-06-26"},{"cvss_score":6.1,"headline":"Cross-site scripting in Apache Roller","id":"CVE-2019-0234","kev_date_added":null,"published":"2019-07-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["Apache Software Foundation"]},"summary":"Attackers can exploit SSRF and file enumeration via XML-RPC interface, even if disabled in UI, by leveraging Java SAX parser external entity support.","url":"https://insights.sbomify.com/CVE-2018-17198/"}