AnsibleApplication · Redhat
CVE-2019-10206
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 · uneditedansible-playbook -k and ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special characters. Passwords should be wrapped to prevent templates trigger and exposing them.
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 confidenceThe ansible CLI tools (particularly ansible-playbook with the -k flag) process password inputs through Jinja2 template expansion. When users enter passwords containing special template characters (like {{ or }}), these characters trigger template interpretation instead of being treated as literal password characters, potentially exposing or modifying the actual password value.
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
AnsibleApplication
>= 2.6.0, < 2.6.19>= 2.7.0, < 2.7.13>= 2.8.0, < 2.8.4
Debian LinuxOperating system
= 10.0= 15.0= 15.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Ansible versionRun `ansible --version` and look for the version number in the first line output (format is like 2.7.0, 2.8.3, 2.6.15)Affected if The version is >= 2.6.0 and < 2.6.19, OR >= 2.7.0 and < 2.7.13, OR >= 2.8.0 and < 2.8.4
-
Verify Ansible CLI usage with -k flagReview your ansible-playbook commands or shell history for usage of the -k flag, which enables SSH password promptingAffected if You run ansible-playbook or related CLI tools with the -k flag to prompt for passwords
-
Identify passwords with template charactersDetermine whether any passwords you enter when prompted by the -k flag contain the literal character sequences {{ or }}Affected if Passwords entered at the -k prompt contain the Jinja2 template characters {{ or }} as part of the password value
You are affected if your installed Ansible version falls within the vulnerable ranges and you use the -k flag with passwords containing {{ or }} characters
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 data2.6.192.7.132.8.4
Upgrade Ansible to the patched versions (2.8.4+, 2.7.13+, or 2.6.19+) to ensure passwords are properly wrapped before template expansion occurs, preventing special characters from triggering template processing.
Fix this in Ansible
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10206 — 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-2019-10206 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