AnsibleApplication · Redhat
CVE-2017-7550
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 · uneditedA flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters to the jenkins_plugin module. Remote attackers could use this flaw to expose sensitive information from a remote host's logs. This flaw was fixed by not allowing passwords to be specified in the "params" argument, and noting this in the module documentation.
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 jenkins_plugin module in Ansible versions 2.3.x before 2.3.3 and 2.4.x before 2.4.1 was passing certain parameters (including passwords) directly to the underlying Jenkins API, which caused these sensitive values to be written to remote host logs. This allowed remote attackers with access to those logs to obtain credentials and other sensitive information.
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.3.0, < 2.3.3>= 2.4.0, < 2.4.1
Enterprise Linux ServerOperating system
= 7.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ansible versionRun command: ansible --version or ansible-playbook --versionAffected if Version is >= 2.3.0 and < 2.3.3, or >= 2.4.0 and < 2.4.1
-
Find playbooks using jenkins_plugin moduleSearch playbook files for 'jenkins_plugin' module usage, for example: grep -r 'jenkins_plugin' /path/to/playbooks/Affected if Any playbook uses the jenkins_plugin module
-
Inspect jenkins_plugin usage for exposed passwordsReview identified playbooks and check if the 'params' argument contains sensitive values like passwords or API keys directlyAffected if Passwords or sensitive parameters are passed directly through the 'params' argument in jenkins_plugin tasks
-
Search logs for leaked credentialsExamine remote host logs (such as /var/log/messages, /var/log/ansible.log, or journalctl) for instances where password or sensitive parameter values appear in plain textAffected if Plain-text passwords or sensitive values appear in logs on managed hosts
A user is affected if they run a vulnerable Ansible version (2.3.0-2.3.2 or 2.4.0) AND use the jenkins_plugin module with sensitive parameters passed through the 'params' argument, potentially leaking those values to host logs.
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.
dbcve · scoped2.3.32.4.1
Upgrade Ansible to version 2.3.3 or later for the 2.3 branch, or 2.4.1 or later for the 2.4 branch. Alternatively, review all playbooks using the jenkins_plugin module and ensure passwords are not passed through the 'params' argument; use the dedicated 'params' field or environment variables instead.
Ansible 2.3.3 or 2.4.1 (or later stable releases)
- 1. Check current Ansible version: ansible --version
- 2. If running Ansible 2.3.x (versions 2.3.0 through 2.3.2), upgrade to Ansible 2.3.3 or later
- 3. If running Ansible 2.4.x (versions 2.4.0), upgrade to Ansible 2.4.1 or later
- 4. If using the jenkins_plugin module, ensure passwords are passed via the dedicated 'password' parameter rather than the 'params' argument
- 5. Verify the upgrade: ansible --version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ansible
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7550 — 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-2017-7550 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