dbcve.org
NodeOperating system · Ovirt

CVE-2013-0293

HIGH · 7.8 CVSS v3.1 Published 2019-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Node: Lock screen accepts F2 to drop to shell causing privilege escalation

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

The oVirt Node lock screen can be bypassed by pressing F2, which drops the user to a shell with elevated privileges. This allows an attacker with physical or console access to escape the lock screen and gain unauthorized system access.

MitigationDisable or properly handle the F2 key during the locked state in the oVirt Node lock screen implementation to prevent shell access bypass.

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
NodeOperating system
Affected:= 2.6.0-1

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

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if oVirt Node is installed
    Check for oVirt Node installation by looking for ovirt-node package or related files, typically in /usr/bin/ or /opt/ovirt* directories
    Affected if oVirt Node version 2.6.0-1 is found on the system
  2. Verify the installed oVirt Node version
    Run package query command such as 'rpm -qa | grep ovirt-node' or 'dpkg -l | grep ovirt-node' depending on package manager
    Affected if Installed version equals exactly 2.6.0-1
  3. Check if lock screen functionality is in use
    Inspect whether oVirt Node lock screen is enabled by examining configuration files in /etc/ovirt-node/ or /var/lib/ovirt-node/ directories
    Affected if Lock screen is enabled and accessible at the console
  4. Verify F2 key handling in lock screen
    Attempt to press F2 at the lock screen or examine the lock screen source code/keyhandler configuration for F2 key binding
    Affected if F2 key drops to an elevated shell rather than being disabled or handled securely

A system is affected if it runs oVirt Node version 2.6.0-1 with the lock screen enabled and the F2 key is not properly handled to prevent shell access bypass.

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

Disable or properly handle the F2 key during the locked state in the oVirt Node lock screen implementation to prevent shell access bypass.

Fix this in Node Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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