DAG log disclosure via unauthenticated log server
Published Aug 16, 2021 · Updated Aug 4, 2024
Information disclosure in Apache Airflow before 2.1.2 allows remote attackers to read DAG job logs through the worker log server. When remote logging is disabled, serve_logs starts a Flask application on the worker or scheduler, binds it to 0.0.0.0, and returns requested log files without authenticating the caller. Exposure requires CeleryExecutor or LocalExecutor with the log server reachable; access is read-only, but DAG logs can contain sensitive data.
Summary
What happened
Information disclosure in Apache Airflow before 2.1.2 allows remote attackers to read DAG job logs through the worker log server. When remote logging is disabled, serve_logs starts a Flask application on the worker or scheduler, binds it to 0.0.0.0, and returns requested log files without authenticating the caller. Exposure requires CeleryExecutor or LocalExecutor with the log server reachable; access is read-only, but DAG logs can contain sensitive data.
The record
- CVE
- CVE-2021-35936
- Published
- Aug 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-306, CWE-200, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Airflow <2.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo