Ovirt EngineApplication · Redhat
CVE-2016-3113
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 · uneditedCross-site scripting (XSS) vulnerability in ovirt-engine allows remote attackers to inject arbitrary web script or HTML.
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 confidenceA cross-site scripting (XSS) vulnerability exists in ovirt-engine that allows remote attackers to inject arbitrary web script or HTML via unsanitized user input fields in the web interface.
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
all versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check if ovirt-engine package is installedRun 'rpm -qa | grep ovirt-engine' or check for the service with 'systemctl list-units | grep ovirt'Affected if The ovirt-engine package is present on the system
-
Determine the installed ovirt-engine versionRun 'rpm -q ovirt-engine' to get the exact version number, or check the package details with 'rpm -qi ovirt-engine'Affected if Any version of ovirt-engine is installed (all versions are affected)
-
Verify the ovirt-engine web service is runningRun 'systemctl status ovirt-engine' or check if port 443/80 is listening with 'netstat -tlnp | grep -E ':(80|443)'Affected if The ovirt-engine web service is active and listening
-
Confirm web interface accessibilityCheck if the ovirt-engine web UI ports are exposed to network interfaces using 'ss -tlnp' or by attempting a local curl to the web interface URLAffected if The web interface is reachable (vulnerability is only exploitable through the web UI)
-
Identify active user input forms in the web UILog into the ovirt-engine admin portal and review user-facing input fields such as VM names, descriptions, or custom properties where unsanitized input could be stored and renderedAffected if User input fields exist and are accessible in the web interface
If ovirt-engine is installed with its web interface enabled and accessible, the environment is affected by CVE-2016-3113 since all versions contain the XSS vulnerability in unsanitized user input fields.
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 dataApply available patches for CVE-2016-3113; implement proper input validation and output encoding for all user-supplied data rendered in web pages.
Fix this in Ovirt Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3113 — 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-2016-3113 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