rocketmq-broker-4.6.0.jar: 1 vulnerabilities (highest severity is: 5.3) - autoclosed

[dev-mend-for-github-com[bot]]

Vulnerable Library - rocketmq-broker-4.6.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /pository/org/apache/rocketmq/rocketmq-broker/4.6.0/rocketmq-broker-4.6.0.jar

Found in HEAD commit: 7f4058b287a628770511e70de45e75c2ef034afb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in	Remediation Available
CVE-2019-17572	Medium	5.3	rocketmq-broker-4.6.0.jar	Direct	4.6.1	✅

Details

CVE-2019-17572

### Vulnerable Library - rocketmq-broker-4.6.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /pository/org/apache/rocketmq/rocketmq-broker/4.6.0/rocketmq-broker-4.6.0.jar

Dependency Hierarchy: - :x: **rocketmq-broker-4.6.0.jar** (Vulnerable Library)

Found in HEAD commit: 7f4058b287a628770511e70de45e75c2ef034afb

Found in base branch: main

### Vulnerability Details

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.

Publish Date: 2020-05-14

URL: CVE-2019-17572

### CVSS 3 Score Details (5.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://rocketmq.apache.org/release_notes/release-notes-4.6.1/

Release Date: 2020-05-15

Fix Resolution: 4.6.1

:rescue_worker_helmet: Automatic Remediation is available for this issue

---

:rescue_worker_helmet: Automatic Remediation is available for this issue.

[dev-mend-for-github-com[bot]]

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.

[dev-mend-for-github-com[bot]]

:information_source: This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.

[dev-mend-for-github-com[bot]]

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.

[dev-mend-for-github-com[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[dev-mend-for-github-com[bot]]

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.