AirflowApplication · Apache
CVE-2020-17513
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Airflow versions prior to 1.10.13 contain a Server-Side Request Forgery (SSRF) vulnerability in the Charts and Query View components of the legacy Flask-admin based web UI. Attackers could exploit this to make the Airflow server request arbitrary internal or external resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AirflowApplication
< 1.10.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Airflow versionRun `airflow version` or check the installed package version via pip (`pip show apache-airflow`) or your package managerAffected if The version is lower than 1.10.13 (e.g., 1.10.12, 1.10.11, etc.)
-
Verify the legacy Flask-admin web UI is enabledCheck your Airflow configuration (airflow.cfg) for the `[webserver]` section. Look for `base_url` configuration and confirm the webserver is running. The legacy UI uses Flask-Admin and is enabled by default in affected versions.Affected if The webserver is running and accessible (the vulnerable component is part of the default web UI in versions prior to 1.10.13)
-
Confirm Charts or Query View endpoints are accessibleAttempt to access the legacy UI endpoints: `<your-airflow-url>/chart/`, `<your-airflow-url>/query/`, or navigate to the Charts and Query views in the legacy web UI navigationAffected if These endpoints are reachable without additional authentication beyond Airflow's standard auth (the SSRF can be triggered through these views)
You are affected if you are running any Airflow version prior to 1.10.13 and have the legacy Flask-admin web UI accessible with Charts or Query View enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.10.13
Upgrade Apache Airflow to version 1.10.13 or later to obtain the security fix. If immediate upgrade is not feasible, restrict network access to the legacy Airflow UI and consider disabling it if not needed.
Fix this in Airflow
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-17513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data