dbcve.org
Ovirt EngineApplication · Redhat

CVE-2015-1780

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 users with MANIPULATE_STORAGE_DOMAIN permissions can attach a storage domain to any data-center

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 · moderate confidence

This is an authorization bypass vulnerability in oVirt where users granted the MANIPULATE_STORAGE_DOMAIN permission can attach storage domains to any data center in the environment, regardless of whether they have proper authorization for those data centers. The permission check for attaching storage domains does not properly validate the user's authorization for the target data center.

MitigationImplement proper authorization checks to verify that users have appropriate permissions for the specific data center before allowing storage domain attachment operations.

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
Affected:all versions
VirtualizationApplication
Affected:= 3.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 or Red Hat Virtualization is installed
    Check the installed version of oVirt Engine (engine-version command) or Red Hat Virtualization (rpm -q rhvm). Compare the version against the affected ranges: oVirt Engine all versions, Red Hat Virtualization 3.0.
    Affected if The installed version falls within Red Hat Virtualization 3.0 or any version of oVirt Engine.
  2. Determine if MANIPULATE_STORAGE_DOMAIN permission exists
    Access the oVirt/RHV administration portal and navigate to Configure > Permissions. Search for roles or permissions that include the MANIPULATE_STORAGE_DOMAIN action. Alternatively, query the database: SELECT role_name FROM roles WHERE allowed_actions LIKE '%MANIPULATE_STORAGE_DOMAIN%';
    Affected if Any role or permission grants MANIPULATE_STORAGE_DOMAIN to users.
  3. Verify storage domain attachment authorization controls
    Review the authorization logic for storage domain attachment operations. Check if the system validates both storage domain permissions AND data center permissions before allowing attachment. Inspect the VdcActionType or equivalent backend code for AttachStorageDomain operations to see if DataCenter authorization is explicitly checked.
    Affected if The system does NOT validate the user's authorization for the target data center before allowing storage domain attachment.
  4. Check for unauthorized storage domain attachments
    Review storage domain attachment logs and audit trails in the engine audit.log or database (SELECT * FROM storage_domain_static; JOIN...). Identify any attachments where the user lacks DataCenter-level permissions.
    Affected if Storage domains have been attached to data centers by users who lack proper DataCenter authorization but have MANIPULATE_STORAGE_DOMAIN permission.

A user is affected if they run any version of oVirt Engine or Red Hat Virtualization 3.0, and their environment has users with MANIPULATE_STORAGE_DOMAIN permission who can attach storage domains without data center-level authorization validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks to verify that users have appropriate permissions for the specific data center before allowing storage domain attachment operations.

Fix this in Ovirt Engine Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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