Ovirt EngineApplication · Redhat
CVE-2020-10775
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 · uneditedAn Open redirect vulnerability was found in ovirt-engine versions 4.4 and earlier, where it allows remote attackers to redirect users to arbitrary web sites and attempt phishing attacks. Once the target has opened the malicious URL in their browser, the critical part of the URL is no longer visible. The highest threat from this vulnerability is on confidentiality.
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 confidenceAn open redirect vulnerability in ovirt-engine versions 4.4 and earlier allows remote attackers to craft malicious URLs that appear to originate from the legitimate ovirt-engine domain but redirect users to arbitrary external websites for phishing attacks. The vulnerability exploits insufficient validation of redirect parameters, and the malicious destination becomes obscured once the browser loads the page.
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.4= 4.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/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 if ovirt-engine is installedRun 'rpm -qa | grep ovirt-engine' or check for /etc/ovirt-engine directory existenceAffected if ovirt-engine package or directory is found on the system
-
Determine the installed ovirt-engine versionRun 'rpm -q ovirt-engine' or 'engine-version' command if available, or inspect the version file in /usr/share/ovirt-engine/libAffected if Version returned is 4.4 or earlier for Red Hat Ovirt, or exactly 4.0 for Oracle Virtualization
-
Verify the web interface is accessibleConfirm the ovirt-engine web application is running by accessing the URL (typically port 443/8443) and checking for ovirt-engine login pageAffected if The web interface is exposed and accessible
-
Inspect redirect parameters in useReview web server logs or proxy configurations for redirect URL parameters (such as 'redirect=', 'url=', 'next=') being passed to ovirt-engine endpointsAffected if Redirect parameters are being processed by the application without validation
The environment is affected if ovirt-engine or Oracle Virtualization is installed with a version at or below 4.4 (Red Hat) or exactly 4.0 (Oracle), and the web interface processes redirect parameters.
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 dataUpgrade ovirt-engine to a version that includes the security fix, or implement strict validation of redirect URL parameters to ensure only relative/internal paths are allowed.
Fix this in Ovirt Engine
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10775 — 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-2020-10775 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