Chartbrew is an open-source web application that can connect directly to databases and APIs and use…

Why it is Yellow

• CVSS 7.0 high

References

• https://github.com/chartbrew/chartbrew/commit/8cfac8076bb0001b1571d93ef923698f53767751
• https://github.com/chartbrew/chartbrew/releases/tag/v5.2.1
• https://github.com/chartbrew/chartbrew/security/advisories/GHSA-6m7q-jmp7-3vw8

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.1, the outbound URL guard recognized ordinary IPv4, IPv6, and IPv4-mapped IPv6 destinations but did not recognize IPv4 addresses embedded in NAT64 prefixes. The vulnerable surface is aPI Data Connection outbound requests routed through server/modules/outboundTargetPolicy.js. An authenticated user with permission to create or edit an API connection supplies an attacker-controlled hostname or redirect whose DNS answer is a NAT64 address embedding a private or link-local IPv4 destination. The policy treated the NAT64 address as public; a NAT64 gateway then translated it to the embedded private IPv4 address after validation. The bypass requires a NAT64/DNS64 deployment path and connection-management privileges. IPv4-only deployments are not affected by this specific bypass. The attacker can read responses from 169.254.169.254 cloud metadata and arbitrary internal IPv4 hosts and ports reachable through the NAT64 gateway. This issue is fixed in version 5.2.1.