When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+ Users are recommended to upgrade to version 3.2.0, which fixes this issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NApache Airflow
APPApache3.0.0 – 3.2.0 (bez)
Related vulnerabilities
The previous default setting for Airflow's Experimental API was to allow all API requests without authenticati...
Apache Airflow: command injection przez niebezpieczny wzorzec w dokumentacji BashOperator
Apache Airflow Providers FAB — nieprawidłowe wygasanie sesji (CWE-613)
Privilege Context Switching Error vulnerability in Apache Software Foundation Apache Airflow.This issue affect...
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache So...