VirtualizationApplication · Redhat
CVE-2018-1073
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 · uneditedThe web console login form in ovirt-engine before version 4.2.3 returned different errors for non-existent users and invalid passwords, allowing an attacker to discover the names of valid user accounts.
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-engine web console login form prior to version 4.2.3 exhibited different error responses for non-existent usernames versus incorrect passwords, enabling an unauthenticated attacker to enumerate valid user accounts through repeated login attempts.
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
VirtualizationApplication
= 4.0
Virtualization HostApplication
= 4.0< 4.2.3CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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-engine package versionRun 'rpm -q ovirt-engine' or 'rpm -qa | grep ovirt-engine' to retrieve the installed package versionAffected if Version is lower than 4.2.3 (e.g., 4.2.0 through 4.2.2) or cannot be determined to be 4.2.3 or higher
-
Check Redhat Virtualization host versionRun 'rpm -q rhev-hypervisor' or check the host system version informationAffected if Version is 4.0 and the ovirt-engine web console is accessible on the network
-
Verify web console is accessibleConfirm the ovirt-engine web interface (typically on port 443/443) is reachable - check with 'curl -k https://<engine-host>/ovirt-engine/' or via browserAffected if The web console is exposed and accessible externally or to untrusted networks
-
Test login error message uniformity (authorized test only)Using a test account, attempt two login attempts: one with a definitely-nonexistent username and one with a valid username but wrong password. Compare the error messages displayed.Affected if The error messages differ between the two cases (e.g., 'User does not exist' vs 'Incorrect password' instead of generic 'Invalid credentials' for both)
You are affected if the ovirt-engine version is below 4.2.3 AND the web console login form displays distinct error messages for invalid usernames versus incorrect passwords, allowing user enumeration.
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.
From vendor data4.2.3
Upgrade ovirt-engine to version 4.2.3 or later, which implements uniform error messaging for both invalid usernames and incorrect passwords.
Fix this in Virtualization
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1073 — 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-1073 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