| CVE-2022-41672 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow, prior to version 2.4.1, deactivating a user wouldn't prevent an already authenticated user from being able to continue using the UI or API. |
| CVE-2022-40604 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow 2.3.0 through 2.3.4, part of a url was unnecessarily formatted, allowing for possible information extraction. |
| CVE-2022-40754 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow 2.3.0 through 2.3.4, there was an open redirect in the webserver's `/confirm` endpoint. |
| CVE-2022-38170 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow prior to 2.3.4, an insecure umask was configured for numerous Airflow components when running with the `--daemon` flag which could result in a race condition giving world-writable f… |
| CVE-2022-38054 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow versions 2.2.4 through 2.3.3, the `database` webserver session backend was susceptible to session fixation. |
| CVE-2021-38540 |
unknown |
— |
— |
|
|
|
4y ago |
The variable import endpoint was not protected by authentication in Airflow >=2.0.0, <2.1.3. This allowed unauthenticated users to hit that endpoint to add/modify Airflow variables used in DAGs, pote… |
| CVE-2017-12614 |
unknown |
— |
— |
|
|
|
4y ago |
It was noticed an XSS in certain 404 pages that could be exploited to perform an XSS attack. Chrome will detect this as a reflected XSS attempt and prevent the page from loading. Firefox and other br… |
| CVE-2021-45229 |
unknown |
— |
— |
|
|
|
4y ago |
It was discovered that the "Trigger DAG with config" screen was susceptible to XSS attacks via the `origin` query argument. This issue affects Apache Airflow versions 2.2.3 and below. |
| CVE-2022-24288 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI. |
| CVE-2021-45230 |
unknown |
— |
— |
|
|
|
4y ago |
In Apache Airflow prior to 2.2.0. This CVE applies to a specific case where a User who has "can_create" permissions on DAG Runs can create Dag Runs for dags that they don't have "edit" permissions fo… |
| CVE-2021-35936 |
unknown |
— |
— |
|
|
|
5y ago |
If remote logging is not used, the worker (in the case of CeleryExecutor) or the scheduler (in the case of LocalExecutor) runs a Flask logging server and is listening on a specific port and also bind… |
| CVE-2021-28359 |
unknown |
— |
— |
|
|
|
5y ago |
The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions <1.10.15 in 1.x series and affects 2.0.0 and 2.0.1 and… |
| CVE-2021-26697 |
unknown |
— |
— |
|
|
|
5y ago |
The lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as th… |
| CVE-2020-13944 |
unknown |
— |
— |
|
|
|
5y ago |
In Apache Airflow < 1.10.12, the "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. |
| CVE-2020-17526 |
unknown |
— |
— |
|
|
|
5y ago |
Incorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Air… |
| CVE-2020-17515 |
unknown |
— |
— |
|
|
|
5y ago |
The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.13. This is same as CVE-2020-13944 but t… |
| CVE-2021-26559 |
unknown |
— |
— |
|
|
|
5y ago |
Improper Access Control on Configurations Endpoint for the Stable API of Apache Airflow allows users with Viewer or User role to get Airflow Configurations including sensitive information even when `… |
| CVE-2020-17513 |
unknown |
— |
— |
|
|
|
6y ago |
In Apache Airflow versions prior to 1.10.13, the Charts and Query View of the old (Flask-admin based) UI were vulnerable for SSRF attack. |
| CVE-2020-17511 |
unknown |
— |
— |
|
|
|
6y ago |
In Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. Same happened when creating a Connection w… |
| CVE-2020-9485 |
unknown |
— |
— |
|
|
|
6y ago |
An issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the "classic" UI. |
| CVE-2020-11981 |
unknown |
— |
— |
|
|
|
6y ago |
An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, res… |
| CVE-2020-11982 |
unknown |
— |
— |
|
|
|
6y ago |
An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious pa… |
| CVE-2020-11983 |
unknown |
— |
— |
|
|
|
6y ago |
An issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated us… |
| CVE-2019-12398 |
unknown |
— |
— |
|
|
|
6y ago |
In Apache Airflow before 1.10.5 when running with the "classic" UI, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain … |
| CVE-2019-12417 |
unknown |
— |
— |
|
|
|
7y ago |
A malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. This also presented a Local File Disclosure vulnerabilit… |
| CVE-2019-0229 |
unknown |
— |
— |
|
|
|
7y ago |
A number of HTTP endpoints in the Airflow webserver (both RBAC and classic) did not have adequate protection and were vulnerable to cross-site request forgery attacks. |
| CVE-2019-0216 |
unknown |
— |
— |
|
|
|
7y ago |
A malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. |
| CVE-2018-20244 |
unknown |
— |
— |
|
|
|
7y ago |
In Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. |
| CVE-2018-20245 |
unknown |
— |
— |
|
|
|
8y ago |
The LDAP auth backend (airflow.contrib.auth.backends.ldap_auth) prior to Apache Airflow 1.10.1 was misconfigured and contained improper checking of exceptions which disabled server certificate checki… |
| CVE-2017-17835 |
unknown |
— |
— |
|
|
|
8y ago |
In Apache Airflow 1.8.2 and earlier, a CSRF vulnerability allowed for a remote command injection on a default install of Airflow. |
| CVE-2017-17836 |
unknown |
— |
— |
|
|
|
8y ago |
In Apache Airflow 1.8.2 and earlier, an experimental Airflow feature displayed authenticated cookies, as well as passwords to databases used by Airflow. An attacker who has limited access to airflow,… |
| CVE-2017-15720 |
unknown |
— |
— |
|
|
|
8y ago |
In Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object. |
