AnsibleApplication · Jenkins
CVE-2018-1000149
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 man in the middle vulnerability exists in Jenkins Ansible Plugin 0.8 and older in AbstractAnsibleInvocation.java, AnsibleAdHocCommandBuilder.java, AnsibleAdHocCommandInvocationTest.java, AnsibleContext.java, AnsibleJobDslExtension.java, AnsiblePlaybookBuilder.java, AnsiblePlaybookStep.java that disables host key verification by default.
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 Ansible Plugin 0.8 and older disables SSH host key verification by default across multiple components (AbstractAnsibleInvocation.java, AnsibleAdHocCommandBuilder.java, etc.). This allows man-in-the-middle attackers to intercept SSH connections from Ansible playbooks, potentially capturing credentials or injecting malicious commands.
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
<= 0.8CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm Jenkins Ansible Plugin installationNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory at JENKINS_HOME/plugins/ansible/Affected if The Jenkins Ansible Plugin is present in the Jenkins instance
-
Identify installed Ansible Plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, locate the Ansible Plugin and record the version number. Compare against affected range: <= 0.8Affected if Installed version is 0.8 or any version lower than 0.8
-
Examine global Ansible configuration for host key settingsGo to Jenkins > Configure System > Ansible section (or Manage Jenkins > Global Configuration > Ansible), look for SSH host key verification options such as 'host key checking', 'known hosts file', or 'lookup_host_key' settingsAffected if Host key verification is disabled, not configured, or set to a permissive value (for example, 'no' or unchecked)
-
Review job-level Ansible build step configurationsInspect individual Jenkins jobs that use Ansible build steps (Ansible Playbook builder, Ansible Ad-Hoc command builder), check for host key verification settings in each job's configurationAffected if Host key verification is disabled in job-level configurations or uses insecure defaults
The environment is affected if the Jenkins Ansible Plugin version is 0.8 or lower AND SSH host key verification is disabled or not explicitly enabled in either the global or job-level configuration.
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 dataEnable SSH host key verification in the Jenkins Ansible Plugin configuration or upgrade to a patched version that enforces host key checking by default.
Fix this in Ansible
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000149 — 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-2018-1000149 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