{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.rocketmq:rocketmq-broker. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17572 in the wild and no public exploit code.","fix":"Upgrade org.apache.rocketmq:rocketmq-broker to 4.6.1 or later.","what":"CVE-2019-17572 is a medium-severity path traversal vulnerability in Apache RocketMQ, published on 14 May 2020. 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-17572 and fix it if it is affected.\n\nWhat it is: CVE-2019-17572 is a medium-severity path traversal vulnerability in Apache RocketMQ, published on 14 May 2020. 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-17572 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.rocketmq:rocketmq-broker (Maven): affected from 4.2.0; fixed in 4.6.1\n- org.apache.rocketmq:rocketmq-broker (Maven): affected from 4.2.0; fixed in 4.6.1\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-17572/ (Markdown: https://insights.sbomify.com/CVE-2019-17572/index.md)","id":"CVE-2019-17572","markdown":"https://insights.sbomify.com/CVE-2019-17572/index.md","name":"CVE-2019-17572","record":{"aliases":["GHSA-5x3v-2gxr-59m2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Message Queue Broker","requires_auth":"none","summary":"An attacker can create directories outside the intended path by sending a malicious topic name, potentially leading to unauthorized file system modifications.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"rocketmq","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-08-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-16T09:36:51Z","kind":"github_poc","ref":"https://github.com/shoucheng3/apache__rocketmq_CVE-2019-17572_4-6-0","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Directory traversal in Apache RocketMQ","id":"CVE-2019-17572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Reflected Cross-Site Scripting in Apache CXF","id":"CVE-2019-17573"},"packages":[{"ecosystem":"Maven","fixed":["4.6.1"],"introduced":["4.2.0"],"last_affected":[],"package":"org.apache.rocketmq:rocketmq-broker","purl":null,"source":"GHSA-5x3v-2gxr-59m2"},{"ecosystem":"Maven","fixed":["4.6.1"],"introduced":["4.2.0"],"last_affected":[],"package":"org.apache.rocketmq:rocketmq-broker","purl":"pkg:maven/org.apache.rocketmq/rocketmq-broker","source":"GHSA-5x3v-2gxr-59m2"}],"prev":{"headline":"Deserialization of Untrusted Data in Log4j","id":"CVE-2019-17571"},"products":["Apache RocketMQ"],"published":"2020-05-14","related":[{"cvss_score":9.8,"headline":"Apache RocketMQ Command Execution","id":"CVE-2023-33246","kev_date_added":"2023-09-06","published":"2023-05-24"},{"cvss_score":9.8,"headline":"Apache RocketMQ: Possible remote code execution when using the update configuration function","id":"CVE-2023-37582","kev_date_added":null,"published":"2023-07-12"},{"cvss_score":7.5,"headline":"Apache RocketMQ: Unauthorized Exposure of Sensitive Data","id":"CVE-2024-23321","kev_date_added":null,"published":"2024-07-22"}],"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":"An attacker can create directories outside the intended path by sending a malicious topic name, potentially leading to unauthorized file system modifications.","url":"https://insights.sbomify.com/CVE-2019-17572/"}