# CVE-2018-1117: Information disclosure in ovirt-ansible-roles

> Missing no_log directive in Ansible roles exposes admin passwords in logs, potentially leading to privilege escalation in shared environments.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xghx-gh8p-84h2, RHSA-2018:1452

## What is CVE-2018-1117?

CVE-2018-1117 is a medium-severity vulnerability in [UNKNOWN] ovirt-ansible-roles, published on 19 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ovirt-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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-1117?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ovirt-ansible-roles` | Red Hat:rhev_manager:4 | All versions | 0:1.0.6-1.el7ev |

Products: Ovirt Ovirt-Ansible-Roles, Redhat Enterprise Virtualization.

## How do I fix CVE-2018-1117?

Upgrade to a fixed version.

## Is CVE-2018-1117 being exploited?

There is no known exploitation of CVE-2018-1117 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1117 and fix it if it is affected.

What it is: CVE-2018-1117 is a medium-severity vulnerability in [UNKNOWN] ovirt-ansible-roles, published on 19 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1117 in the wild and no public exploit code.

Affected product: [UNKNOWN] ovirt-ansible-roles. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1117/ (Markdown: https://insights.sbomify.com/CVE-2018-1117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1117
- OSV: https://osv.dev/vulnerability/CVE-2018-1117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1117/
Summaries are generated and may contain mistakes; the official description above is the record.