CVE-2022-37425
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 · uneditedImproper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in OpenNebula OpenNebula core on Linux allows Remote Code Inclusion.
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 command injection vulnerability in OpenNebula core on Linux allows remote attackers to execute arbitrary OS commands by injecting malicious commands through unsanitized input fields. The critical CVSS score of 9.8 reflects the ability to achieve remote code execution without authentication.
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< 6.4.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if OpenNebula is installedLook for OpenNebula binaries and directories. Common paths include /usr/bin/one*, /etc/one/, /var/lib/one/. Run: which one one_xmlrpc oned 2>/dev/null; ls -la /etc/one/ 2>/dev/null; ls -la /var/lib/one/ 2>/dev/nullAffected if OpenNebula binaries or configuration directories are found on the system
-
Determine installed OpenNebula versionRun the version command for OpenNebula. Try: oned --version 2>/dev/null || oneversion 2>/dev/null || rpm -q opennebula 2>/dev/null || dpkg -l opennebula 2>/dev/nullAffected if The installed version is identified as less than 6.4.2 (e.g., 6.4.1, 6.4.0, 6.2.x, 5.x)
-
Check if OpenNebula services are running and exposedCheck if the OpenNebula XML-RPC interface or Sunstone web service is listening. Run: netstat -tlnp 2>/dev/null | grep -E '2633|29876' or ss -tlnp | grep -E '2633|29876'Affected if Ports 2633 (XML-RPC) or 29876 (Sunstone) are listening and accessible from network segments where attackers could reach them
-
Identify input fields exposed to unauthenticated usersReview OpenNebula configuration files in /etc/one/ to determine if the XML-RPC API or Sunstone interface is configured without requiring authentication or is exposed to untrusted networks. Check: cat /etc/one/sunstone-server.conf 2>/dev/null | grep -i authAffected if The OpenNebula management interface is accessible without authentication or from untrusted network segments
A system is affected if OpenNebula is installed with a version lower than 6.4.2 and its management interface (XML-RPC on port 2633 or Sunstone on port 29876) is exposed to the network.
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.
dbcve · scoped6.4.2
Apply vendor-supplied patches or upgrade to the latest OpenNebula version immediately. Restrict network access to the OpenNebula management interface and implement additional input validation at network boundaries as temporary mitigation.
6.4.2 or later
- Review the official OpenNebula upgrade documentation at opennebula.io for version 6.4.2
- Create a complete backup of the current OpenNebula installation including database, configuration files, and VMs
- Stop the OpenNebula services (oned, sunstone, and related components)
- Upgrade the OpenNebula packages to version 6.4.2 or later using the distribution's package manager
- Run any provided database migration scripts included with the upgrade
- Verify configuration file compatibility and merge any new default settings as needed
- Restart the OpenNebula services
- Verify the installation by checking service status and testing core functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37425 — 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-2022-37425 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