Chartbrew: DNS Rebinding SSRF Bypass in Outbound Request Validation
chartbrew
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| chartbrew chartbrew |
| No fix yet |
Original description
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.2, Chartbrew's server/modules/safeRequest.js calls validateOutboundUrl() to resolve and validate a target hostname, but request-promise performs a separate DNS resolution for the actual connection. An authenticated user who can create or test API connections and controls the target DNS name can return a public address during validation and a private address during the request, bypassing the protections implemented by server/modules/outboundTargetPolicy.js. This DNS rebinding condition can expose internal services, localhost resources, or cloud metadata endpoints. This issue is fixed in version 5.2.2.
From the CVE record · GitHub_M