Ovirt EngineApplication · Redhat
CVE-2017-7510
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 · uneditedIn ovirt-engine 4.1, if a host was provisioned with cloud-init, the root password could be revealed through the REST interface.
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 confidenceIn oVirt Engine 4.1, when hosts are provisioned using cloud-init, the root password is stored and then exposed in plaintext through the REST API due to improper authorization controls. Any authenticated user with REST API access can retrieve the credentials of provisioned hosts.
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
Ovirt EngineApplication
= 4.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify oVirt Engine versionQuery the oVirt Engine version through the administration portal or by checking the engine version file (typically /etc/ovirt-engine/engine-version or via the engine command)Affected if Version is 4.1.0 through 4.1.4 (the flaw was fixed in 4.1.5)
-
Confirm cloud-init host provisioning was usedReview the host provisioning history or configuration in oVirt to determine whether cloud-init was used when adding hosts to the environmentAffected if Cloud-init was used to provision hosts in the environment
-
Verify root password was configured in cloud-initCheck the cloud-init configuration for any hosts that were provisioned to see if a root password was set in the cloud-init template or scriptAffected if A root password was specified in the cloud-init provisioning configuration
-
Confirm REST API access existsVerify that REST API access is enabled and that users or systems have authentication credentials to query the oVirt REST APIAffected if Any authenticated user has REST API access to the oVirt environment
The environment is affected if oVirt Engine version is 4.1.0-4.1.4 AND cloud-init was used to provision hosts with a root password AND the REST API is accessible to authenticated users.
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 dataRestrict REST API access to prevent unauthorized retrieval of cloud-init credentials; upgrade to oVirt 4.1.5 or later where the password is no longer exposed via the REST interface.
Fix this in Ovirt Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7510 — 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-2017-7510 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