dbcve.org
OvirtApplication

CVE-2018-1075

HIGH · 7.8 CVSS v3.0 Published 2018-06-12
Fix available
A fix is available. Upgrade to 4.2.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
ovirt-engine up to version 4.2.3 is vulnerable to an unfiltered password when choosing manual db provisioning. When engine-setup was run and one chooses to provision the database manually or connect to a remote database, the password input was logged in cleartext during the verification step. Sharing the provisioning log might inadvertently leak database passwords.

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 confidence

ovirt-engine versions up to 4.2.3 contain a cleartext password logging vulnerability in the engine-setup component. When users choose manual database provisioning or connect to a remote database during setup, the database password is logged in plaintext during the verification step, allowing password extraction from provisioning logs.

MitigationAvoid sharing engine-setup logs publicly; filter or redact database passwords from logs before sharing. Upgrade to ovirt-engine 4.2.4 or later where the password filtering was likely implemented.

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
OvirtApplication
Affected:< 4.2.3

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check ovirt-engine version
    Run 'rpm -q ovirt-engine' or check the installed package version through your package manager
    Affected if Installed version is lower than 4.2.3 (e.g., 4.2.0, 4.2.1, 4.2.2)
  2. Locate engine-setup logs
    Search for engine-setup log files in /var/log/ovirt-engine/setup/ or the directory where setup logs were stored during installation
    Affected if Log files exist from a setup run using manual database provisioning or remote database connection
  3. Inspect logs for plaintext passwords
    Open the engine-setup log file and search for the database password string or grep for terms like 'password' or 'pass' near database configuration sections
    Affected if The log contains the actual database password in plaintext rather than masked or filtered characters

You are affected if ovirt-engine version is below 4.2.3 AND engine-setup logs from a manual/remote database provisioning run contain the database password in plaintext.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 4.2.3 or later
Fixed in 4.2.3
Interim mitigation

Avoid sharing engine-setup logs publicly; filter or redact database passwords from logs before sharing. Upgrade to ovirt-engine 4.2.4 or later where the password filtering was likely implemented.

Fix this in Ovirt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1075 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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