Enterprise VirtualizationOperating system · Redhat
CVE-2018-1117
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 · uneditedovirt-ansible-roles before version 1.0.6 has a vulnerability due to a missing no_log directive, resulting in the 'Add oVirt Provider to ManageIQ/CloudForms' playbook inadvertently disclosing admin passwords in the provisioning log. In an environment where logs are shared with other parties, this could lead to privilege escalation.
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 ovirt-ansible-roles Ansible playbook for adding oVirt providers to ManageIQ/CloudForms fails to use the no_log directive, causing admin passwords to be written in plaintext to provisioning logs. Attackers with access to shared logs can retrieve these credentials and gain administrative access.
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
Enterprise VirtualizationOperating system
= 4.1< 1.0.6CVSS 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.0/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 ovirt-ansible-roles installationLocate the ovirt-ansible-roles package in your environment and retrieve its version number using your system package manager or Ansible galaxy commandAffected if The installed version is lower than 1.0.6
-
Find the provider provisioning playbookLocate the Ansible playbook from ovirt-ansible-roles that adds oVirt providers to ManageIQ or CloudForms - typically named something similar to ovirt-providers.yml or within a manageiq/ folderAffected if This playbook exists in your environment and is in use
-
Inspect playbook for no_log directiveOpen the playbook file and search for the task that handles admin credentials - check if the task or its surrounding block includes the no_log: true directiveAffected if The no_log directive is absent from credential-handling tasks in this playbook
-
Search provisioning logs for plaintext passwordsExamine Ansible log files, provisioning logs, and any automation logs where ovirt-ansible-roles playbooks record their output - search for plaintext password strings that match your admin credentialsAffected if Plaintext admin passwords appear in any log files associated with this playbook execution
-
Check for credential exposure in shared log locationsReview log directories accessible to other users or systems - verify if Ansible logs containing provisioning output are readable by parties who should not have credential accessAffected if Logs containing potential plaintext credentials are accessible beyond the intended administrator audience
Your environment is affected if ovirt-ansible-roles version is below 1.0.6 and the provider provisioning playbook has been executed, resulting in plaintext credentials in accessible 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 · scoped1.0.6
Upgrade ovirt-ansible-roles to version 1.0.6 or later where the no_log directive is properly applied. Additionally, audit existing logs for exposed credentials and rotate any compromised passwords immediately.
ovirt-ansible-roles version 1.0.6 or later
- Upgrade ovirt-ansible-roles to version 1.0.6 or later using 'ansible-galaxy install ovirt.ovirt-ansible-roles --version 1.0.6' or equivalent package manager command
- Review all provisioning logs in the environment for any exposed admin passwords
- Rotate any admin passwords that may have been disclosed in logs as a precautionary measure
- Verify the upgrade by checking the playbook now includes 'no_log: true' on sensitive tasks
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Virtualization
Scoped from the published advisory
- Consultation3.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1117 — 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-1117 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