OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform "remote phishing" by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.
OpenBao versions prior to 2.5.2 lack user confirmation prompts during JWT/OIDC login with direct callback mode, enabling attackers to perform remote phishing attacks and hijack user sessions. The vulnerability allows attackers to automatically log victims into attacker-controlled sessions through malicious URLs without user interaction.
يفتقر OpenBao قبل الإصدار 2.5.2 إلى شاشة تأكيد المستخدم عند تسجيل الدخول عبر JWT/OIDC مع وضع الاستدعاء المباشر. يمكن للمهاجمين استغلال هذه الثغرة لإجراء هجمات تصيد احتيالي عن بعد وإجبار الضحايا على تسجيل الدخول إلى جلسات المهاجم تلقائياً. يتطلب الإصلاح ترقية فورية أو تعطيل الأدوار المتأثرة.
OpenBao versions prior to 2.5.2 lack user confirmation prompts during JWT/OIDC login with direct callback mode, enabling attackers to perform remote phishing attacks and hijack user sessions. The vulnerability allows attackers to automatically log victims into attacker-controlled sessions through malicious URLs without user interaction.
Upgrade OpenBao to version 2.5.2 or later immediately. If immediate upgrade is not possible, disable all roles with callback_mode=direct or enforce additional confirmation requirements at the token issuer level. Implement network-based controls to restrict access to OpenBao authentication endpoints.
قم بترقية OpenBao إلى الإصدار 2.5.2 أو أحدث فوراً. إذا لم يكن الترقية الفورية ممكنة، قم بتعطيل جميع الأدوار التي تحتوي على callback_mode=direct أو فرض متطلبات تأكيد إضافية على مستوى مُصدر الرمز. طبق عناصر تحكم قائمة على الشبكة لتقييد الوصول إلى نقاط نهاية المصادقة في OpenBao.