همهٔ گزارش‌ها
زیاد

ZITADEL has LDAP Filter Injection in Login Flow

متن اصلی

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

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

نسخه‌های متأثر
>= 3.1.0, <= 3.4.9
نسخهٔ اصلاح‌شده
3.4.10
نسخه‌های متأثر
>= 2.71.11, <= 2.71.19
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
*
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
>= 4.0.0, <= 4.14.0
نسخهٔ اصلاح‌شده
4.15.0

بهره‌برداری

CVE-2026-44671

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

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

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

Summary

A vulnerability was discovered in Zitadel's LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process.

Impact

While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as *, (, )) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory.

Note that an authentication bypass is not possible.

Affected Versions

Systems integrating LDAP as IdPs and running one of the following versions are affected:

  • 4.x: 4.0.0 through 4.14.0 (including RC versions)

  • 3.x: 3.1.0 through 3.4.9

  • 2.x: 2.71.11 through 2.71.19

Patches

The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address, resp. phone number itself.

Workarounds

The recommended solution is to upgrade to a patched version. If an immediate upgrade is not possible, developers should ensure their project's LDAP directory has strict access controls to limit the scope of information disclosure.

Questions

If there are any questions or comments about this advisory, please send an email to security@zitadel.com

Credits

This vulnerability was identified and reported by ProScan AppSec (https://proscan.one/).

پیوندها

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

  • Proscan-one
  • livio-a
  • wim07101993