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

authentik's invitation expiry is delayed by at least 5 minutes

متن اصلی

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

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

نسخه‌های متأثر
< 0.0.0-20251119135424-6672e6aaa41e
نسخهٔ اصلاح‌شده
0.0.0-20251119135424-6672e6aaa41e
نسخه‌های متأثر
*
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2025-64708

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

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

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

Summary

In previous authentik versions, invitations were considered valid regardless if they are expired or not, thus relying on background tasks to clean up expired ones. In a normal scenario this can take up to 5 minutes because the cleanup of expired objects is scheduled to run every 5 minutes. However, with a large amount of tasks in the backlog, this might take longer.

Patches

authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.

Workarounds

Users can create a policy that explicitly checks whether the invitation is still valid, and then bind it to the invitation stage on your invitation flow, and deny access if the invitation is not valid.

return not context['flow_plan'].context['invitation'].is_expired
For more information

If users have any questions or comments about this advisory:

  • Email the authentik team at security@goauthentik.io.

پیوندها

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

  • melizeche