Apache Airflow's `JWTRefreshMiddleware` set the JWT auth cookie without the `Secure` flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g. nginx / Envoy / a managed load balancer that terminates TLS and forwards plaintext to the API server, the default cloud-native topology) would have the user's session JWT replayed over any cleartext HTTP request to the same host. A network-positioned attacker (Wi-Fi MITM, hostile LAN, captive-portal proxy) could induce a logged-in user's browser to issue an HTTP request to the deployment's hostname and capture the JWT cookie out of that request, then replay it against the authenticated API. Affects deployments where the Airflow API server is reached through a TLS-terminating proxy and the cookie's secure-by-default protection is load-bearing for session integrity. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Apache Airflow's JWTRefreshMiddleware fails to set the Secure flag on JWT authentication cookies, allowing session token interception in HTTPS-terminating reverse proxy deployments. Network-positioned attackers can capture and replay JWT cookies via cleartext HTTP requests to compromise user sessions.
يفشل Apache Airflow في تعيين علم Secure على ملفات تعريف JWT، مما يسمح باعتراض الرموز في بيئات الوكيل العكسي الذي ينهي HTTPS. يمكن للمهاجمين في الشبكة التقاط وإعادة تشغيل ملفات تعريف JWT عبر طلبات HTTP غير المشفرة للوصول إلى واجهات برمجة التطبيقات المصرح بها.
Apache Airflow's JWTRefreshMiddleware fails to set the Secure flag on JWT authentication cookies, allowing session token interception in HTTPS-terminating reverse proxy deployments. Network-positioned attackers can capture and replay JWT cookies via cleartext HTTP requests to compromise user sessions.
Upgrade Apache Airflow to the patched version that sets the Secure flag on JWT authentication cookies. Ensure all Airflow API servers are deployed behind HTTPS-terminating reverse proxies with proper TLS configuration. Implement network segmentation to restrict access to Airflow API endpoints. Monitor for suspicious JWT token usage patterns.
قم بترقية Apache Airflow إلى الإصدار المصحح الذي يعين علم Secure على ملفات تعريف JWT. تأكد من نشر جميع خوادم Airflow API خلف وكلاء عكسيين ينهيان HTTPS مع تكوين TLS مناسب. تنفيذ تقسيم الشبكة لتقييد الوصول إلى نقاط نهاية Airflow API. مراقبة أنماط استخدام رموز JWT المريبة.