CVE-2014-8170
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 · uneditedovirt_safe_delete_config in ovirtfunctions.py and other unspecified locations in ovirt-node 3.0.0-474-gb852fd7 as packaged in Red Hat Enterprise Virtualization 3 do not properly quote input strings, which allows remote authenticated users and physically proximate attackers to execute arbitrary commands via a ; (semicolon) in an input string.
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 confidenceCommand injection vulnerability in ovirt_safe_delete_config function in ovirtfunctions.py where input strings are not properly quoted/sanitized before being passed to shell commands, allowing authenticated users to inject arbitrary commands via semicolon characters.
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= 3.0.0-474-gb852fd7CVSS 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.0/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 if Ovirt Node is installedCheck for ovirt-node package or binary: rpm -qa | grep ovirt-node or dpkg -l | grep ovirt-nodeAffected if Ovirt Node is not installed - not affected
-
Determine installed Ovirt Node versionRun: rpm -qi ovirt-node (or ovirt-node3) and note the Version and Release fieldsAffected if Version is 3.0.0 with Release containing 474-gb852fd7 or earlier (lower than 474-gb852fd7)
-
Locate ovirtfunctions.py fileFind the file: find / -name ovirtfunctions.py 2>/dev/null, typical paths include /usr/share/ovirt-node/ or /usr/lib/python*/site-packages/Affected if File exists and contains ovirt_safe_delete_config function - potential exposure
-
Verify the vulnerable function existsgrep -n 'ovirt_safe_delete_config' /path/to/ovirtfunctions.pyAffected if Function is present - indicates the code path exists for injection
-
Check if web interface or API is accessibleVerify the Ovirt management interface (typically port 443 or 8443) is reachable and requires authenticationAffected if Web interface exposed to authenticated users - injection vector available
System is affected if running Ovirt Node version 3.0.0 with release 474-gb852fd7 or earlier AND the ovirtfunctions.py file contains the ovirt_safe_delete_config function 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 dataApply proper input sanitization and shell escaping to all user-controlled input before executing system calls; audit all unspecified locations mentioned in the advisory for similar injection flaws.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8170 — 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-2014-8170 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