CVE-2019-17572 json
Directory traversal in Apache RocketMQ
published 2020-05-14 6 y ago modified 2026-06-17 4 mo ago also GHSA-5x3v-2gxr-59m2 , EUVD-2020-0539
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
2.99% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.rocketmq:rocketmq-broker | >=4.2.0, <4.6.1 |
4.6.1 |
Affected products
- n/a Apache RocketMQ
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/apache/rocketmq/commit/f8f6fbe4aa7f5dee937e688322628c366b12a552
web
-
lists.apache.org
/thread.html/fdea1c5407da47a17d5522fa149a097cacded1916c1c1534d46edc6d%40%3Cprivate.rocketmq.apache.org%3E
web, broken-link
-
seclists.org
/oss-sec/2020/q2/112
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-17572
advisory
-
github.com
/apache/rocketmq/issues/1637
web
-
snyk.io
/vuln/SNYK-JAVA-ORGAPACHEROCKETMQ-569108
web
Sources
- CVE List CVE-2019-17572
- GitHub Advisory GHSA-5x3v-2gxr-59m2
- NVD CVE-2019-17572
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.