by @LeSuisse Activity log
- Created suggestion
- @LeSuisse dismissed (not in Nixpkgs)
twenty-server SSRF protection bypass via IPv4-mapped IPv6 address normalization
Twenty is an open source CRM built with NestJS (Node.js). In versions 1.18.0 and earlier, the SSRF protection in twenty-server's SecureHttpClientService can be bypassed using IPv4-mapped IPv6 addresses in URL IP literals. Node.js's URL parser normalizes IPv4-mapped IPv6 addresses to compressed hex form (e.g., ::ffff:169.254.169.254 becomes ::ffff:a9fe:a9fe), but the isPrivateIp utility only recognizes the dotted-decimal notation. As a result, the hex form passes the SSRF check unchecked. Additionally, the socket lookup validation event does not fire for IP literal addresses, bypassing the second validation layer. An authenticated user can reach any internal IP, including cloud metadata endpoints, to exfiltrate credentials such as IAM keys.
References
-
https://github.com/twentyhq/twenty/security/advisories/GHSA-vrcj-hv2q-c58m x_refsource_CONFIRM
Affected products
- ==<= 1.18.0
Matching in nixpkgs
pkgs.gnome-2048
Obtain the 2048 tile
pkgs.wordpressPackages.themes.twentytwenty
None
pkgs.wordpressPackages.themes.twentynineteen
None
pkgs.wordpressPackages.themes.twentytwentyone
None
pkgs.wordpressPackages.themes.twentytwentytwo
None
Package maintainers
-
@jtojnar Jan Tojnar <jtojnar@gmail.com>
-
@dasj19 Daniel Șerbănescu <daniel@serbanescu.dk>
-
@bobby285271 Bobby Rong <rjl931189261@126.com>
-
@hedning Tor Hedin Brønner <torhedinbronner@gmail.com>