RockteMQ-AI commented on issue #2336: URL: https://github.com/apache/rocketmq-dashboard/issues/2336#issuecomment-5326024375
Thanks for the clarification, @Aias00. I've verified the code on the `rocketmq-studio` branch and can confirm this is a valid credential disclosure vulnerability. **Verified on `rocketmq-studio` branch:** - `GeneralSettingsVO` exposes `dingtalkWebhook` and `smsWebhook` fields without `@JsonProperty(access = WRITE_ONLY)` - `GET /api/settings/general` serializes these fields in the response - DingTalk/SMS webhook URLs contain access tokens in query strings, allowing reader accounts to obtain reusable credentials - Compare with `apiKey` field which correctly uses `WRITE_ONLY` to prevent serialization **Category:** Security (Credential Disclosure) | **Severity:** MEDIUM **Status:** Confirmed ✓ This should return only configured-state metadata (e.g., `dingtalkWebhookConfigured: true`) rather than raw webhook values, similar to how `apiKey` is handled. -- 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]
