Security readout for executives and security teams
Plain-English summary
Jenkins Ansible Plugin 0.8 and older disabled SSH host key verification by default. That weakens trust between Jenkins automation and target systems, allowing a network-positioned attacker to impersonate hosts and intercept or alter automation traffic.
Executive priority
Prioritize if Jenkins automates privileged infrastructure changes or crosses less-trusted networks. Otherwise handle through normal vulnerability management with upgrade and configuration validation.
Technical view
CVE-2018-1000149 is a man-in-the-middle issue in Jenkins Ansible Plugin code paths including AbstractAnsibleInvocation and Ansible playbook/ad-hoc builders. The issue is the default disabling of host key verification. The source bundle does not provide CVSS, CWE, exploit details, or a named fixed version.
Likely exposure
Exposure is likely limited to Jenkins environments running Ansible Plugin 0.8 or older, especially jobs connecting over networks where attackers could intercept SSH traffic.
Exploitation context
No active exploitation is cited in the provided sources, and the CVE is not marked KEV. Practical exploitation would require network positioning between Jenkins and managed hosts.
Researcher notes
The public bundle identifies the vulnerable behavior and affected version boundary, but lacks CVSS, CWE, exploit evidence, and specific patch details. Avoid assuming exploitation or a fix version beyond vendor guidance.
Mitigation direction
- Inventory Jenkins instances for Ansible Plugin 0.8 or older.
- Check Jenkins advisory and plugin guidance for the supported upgrade path.
- Ensure SSH host key verification is enabled for Ansible-driven jobs.
- Avoid running affected automation across untrusted networks until remediated.
Validation and detection
- Confirm installed Jenkins Ansible Plugin versions across controllers.
- Review Ansible job definitions for affected plugin usage.
- Verify post-remediation jobs enforce SSH host key verification.
- Review relevant job logs for unexpected host identity changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-1000149 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jenkins.io/security/advisory/2018-03-26/#SECURITY-630CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.