dbcve.org
Enterprise Virtualization ManagerApplication · Redhat

CVE-2018-1072

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-26
Fix available
A fix is available. Upgrade to 4.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 before version ovirt 4.2.2 is vulnerable to an information exposure through log files. When engine-backup was run with one of the options "--provision*db", the database username and password were logged in cleartext. 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's engine-backup utility logs database credentials in plaintext when run with provisioning options (--provision*db). The backup tool writes the database username and password directly to log files without masking or redaction, allowing anyone with log access to obtain these credentials.

MitigationUpgrade ovirt-engine to version 4.2.2 or later. Until upgraded, restrict access to provisioning logs and avoid sharing them.

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 Virtualization ManagerApplication
Affected:= 4.2
OvirtApplication
Affected:< 4.2.2

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
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 checks

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

  1. Identify if ovirt-engine is installed
    Check for the presence of the ovirt-engine package or engine-backup utility on the system
    Affected if ovirt-engine is installed and the version falls within the affected range (RHEV 4.2 or Ovirt < 4.2.2)
  2. Determine the installed ovirt-engine version
    Run the appropriate package manager command or check the engine-backup utility version (e.g., engine-backup --version)
    Affected if The version is 4.2 (RHEL/RHEV) or any version prior to 4.2.2 (Ovirt)
  3. Locate engine-backup log files
    Search for log files generated by the engine-backup utility, typically found in standard ovirt-engine log directories
    Affected if Log files exist from backup operations that used --provision*db options
  4. Inspect log files for plaintext credentials
    Examine the contents of engine-backup log files for occurrences of database usernames and passwords in plaintext (search for patterns like 'password=' or actual credential strings)
    Affected if Database credentials appear unmasked or unredacted in the logs
  5. Verify if --provision*db options were used
    Check command history, automation scripts, or log metadata to determine if engine-backup was run with any provisioning options (--provision-db, --provision*db)
    Affected if engine-backup was executed with provisioning options and log files are accessible

A system is affected if ovirt-engine version 4.2 or below (or Ovirt < 4.2.2) is installed AND engine-backup was run with --provision*db options, resulting in plaintext database credentials in accessible log files.

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.

dbcve · scoped
Upgrade available Upgrade to 4.2.2 or later
Fixed in 4.2.2
Interim mitigation

Upgrade ovirt-engine to version 4.2.2 or later. Until upgraded, restrict access to provisioning logs and avoid sharing them.

Recommended fix High confidence

ovirt-engine 4.2.2 or later

  1. Upgrade ovirt-engine to version 4.2.2 or later which contains the fix for CVE-2018-1072
  2. After upgrading, verify that the engine-backup command with --provision*db options no longer writes database credentials to log files
  3. Review the provisioning logs to confirm credentials are no longer exposed in cleartext
  4. If immediate upgrade is not feasible, restrict access to provisioning logs and ensure they are not shared with unauthorized parties until the upgrade can be performed
Caveat Consult the ovirt 4.2.2 release notes for any known breaking changes or migration requirements before performing the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Virtualization Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1072 — 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-1072 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