dbcve.org
OpennebulaApplication

CVE-2022-37426

HIGH · 7.5 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 6.4.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Unrestricted Upload of File with Dangerous Type vulnerability in OpenNebula OpenNebula core on Linux allows File Content Injection.

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

OpenNebula core on Linux contains an unrestricted file upload vulnerability that allows attackers to inject malicious content through file uploads. This appears to be a classic file type validation bypass where the application does not properly validate or restrict the types of files that can be uploaded to the system, potentially enabling arbitrary file content injection.

MitigationImplement strict file type validation using allowlists, validate MIME types and file signatures (magic bytes), store uploaded files outside the web root with randomized names, and enforce proper authentication and authorization checks on upload endpoints.

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
OpennebulaApplication
Affected:< 6.4.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify OpenNebula installation version
    Run 'oneversion' command or check /etc/one/oned.conf for version information, or query the Sunstone API endpoint /version
    Affected if Installed version is lower than 6.4.2
  2. Verify Sunstone web service is running
    Check if the Sunstone service is active using 'systemctl status sunstone' or by querying port 9869 locally
    Affected if Sunstone web interface is exposed and accessible
  3. Check file upload endpoint configuration
    Inspect /etc/sunstone/sunstone-server.conf for upload-related settings such as allowed file extensions or MIME type restrictions
    Affected if No strict file type validation or allowlist is configured for uploads
  4. Review authentication settings on upload APIs
    Examine the Sunstone and OneFlow API configurations for upload endpoints in /etc/one/oned.conf and /etc/sunstone/sunstone-server.conf
    Affected if Upload endpoints do not require authentication or lack proper authorization checks
  5. Inspect uploaded files directory placement
    Check the configuration for the directory where uploaded files are stored (typically under /var/lib/one/datastores/)
    Affected if Uploaded files are stored within the web root or in a publicly accessible location

A system is affected if it runs OpenNebula version lower than 6.4.2 and has the Sunstone web interface enabled with file upload functionality accessible without strict validation controls.

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.

dbcve · scoped
Upgrade available Upgrade to 6.4.2 or later
Fixed in 6.4.2
Interim mitigation

Implement strict file type validation using allowlists, validate MIME types and file signatures (magic bytes), store uploaded files outside the web root with randomized names, and enforce proper authentication and authorization checks on upload endpoints.

Recommended fix High confidence

OpenNebula 6.4.2 or later

  1. 1. Back up the current OpenNebula installation and database before proceeding with the upgrade
  2. 2. Review the official OpenNebula upgrade documentation for your current version to 6.4.x
  3. 3. Ensure all services (sunstone, one, oned) are stopped before upgrade
  4. 4. Upgrade OpenNebula to version 6.4.2 or later following the official upgrade path for your current version
  5. 5. After upgrade, verify that the sunstone web interface is accessible and all services are running
  6. 6. Test file upload functionality to confirm the vulnerability is remediated
Caveat Review upgrade notes between your current version and 6.4.x for potential breaking changes in configuration or API compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opennebula Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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