dbcve.org
AirflowApplication · Apache

CVE-2017-17835

HIGH · 8.8 CVSS v3.0 Published 2019-01-23
Fix available
A fix is available. Upgrade to after 1.8.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
In Apache Airflow 1.8.2 and earlier, a CSRF vulnerability allowed for a remote command injection on a default install of Airflow.

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 confidence

A CSRF vulnerability in Apache Airflow 1.8.2 and earlier allows remote attackers to inject and execute arbitrary commands on the server by tricking authenticated users into submitting malicious requests. This affects default installations where no additional security hardening has been applied.

MitigationUpgrade to Apache Airflow version 1.8.3 or later, which includes CSRF protection tokens and input sanitization to prevent command injection attacks.

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
Affected:<= 1.8.2

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache Airflow version
    Run 'airflow version' command or use pip to query the installed package version
    Affected if Installed version is 1.8.2 or earlier
  2. Verify webserver accessibility
    Confirm the Airflow web server is exposed on a network accessible to untrusted users
    Affected if Web interface is reachable without proper network isolation
  3. Check authentication configuration
    Inspect whether authentication is enabled on the Airflow web server (default installations may have no auth)
    Affected if No authentication is required to access the web interface
  4. Confirm CSRF protection is absent
    Examine web forms and API endpoints for the presence of CSRF tokens - in vulnerable versions, these are not implemented by default
    Affected if Web forms lack CSRF tokens and the Flask-WTF CSRF protection is not configured

Environment is affected if running Apache Airflow 1.8.2 or earlier with default settings where the web interface is accessible and lacks CSRF protection tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.8.2
Interim mitigation

Upgrade to Apache Airflow version 1.8.3 or later, which includes CSRF protection tokens and input sanitization to prevent command injection attacks.

Fix this in Airflow Scoped from the published advisory
  • Consultation8.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
64.0 hours of engineering $11,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-17835 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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