RockteMQ-AI commented on issue #2338: URL: https://github.com/apache/rocketmq-dashboard/issues/2338#issuecomment-5326021447
Thanks for the clarification, @Aias00. I've verified the code on the `rocketmq-studio` branch and can confirm this is a valid SSRF vulnerability. **Verified on `rocketmq-studio` branch:** - `ProxyAddressService.reloadConfig()` accepts any registered `host:port` and POSTs to `http://<addr>/admin/reloadConfig` - The `proxyAddrs` set can be populated via the API, allowing arbitrary target registration - No validation that the target belongs to a known RocketMQ proxy cluster **Category:** Security (SSRF) | **Severity:** MEDIUM (administrator-scoped) **Status:** Confirmed ✓ This should bind reload targets to a trusted, pre-configured proxy allowlist rather than accepting dynamic registration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
