dbcve.org
Starwind San \& NasApplication · Starwindsoftware

CVE-2022-32268

HIGH · 8.8 CVSS v3.1 Published 2022-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
StarWind SAN and NAS v0.2 build 1914 allow remote code execution. A flaw was found in REST API in StarWind Stack. REST command, which allows changing the hostname, doesn’t check a new hostname parameter. It goes directly to bash as part of a script. An attacker with non-root user access can inject arbitrary data into the command that will be executed with root privileges.

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 confidence

Command injection vulnerability in StarWind SAN and NAS REST API hostname change function. The hostname parameter is passed unsanitized directly to a bash script, allowing arbitrary command execution with root privileges by any authenticated non-root user.

MitigationImplement strict input validation and sanitization for the hostname parameter before passing to shell commands. If no patch is available, restrict network access to the REST API and consider disabling the hostname change functionality until a fix is deployed.

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
Starwind San \& NasApplication
Affected:= 0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify if StarWind SAN and NAS is installed
    Look for StarWind installation directories (typically /opt/StarWind or C:\Program Files\StarWind) or check installed packages. On Linux, run: find /opt -name '*tar*' -o -name '*star*' 2>/dev/null; on Windows, check Programs and Features for StarWind.
    Affected if StarWind SAN and NAS software is found on the system
  2. Verify the installed version is 0.2
    Check the StarWind version. On Linux, look for a version file in the installation directory (e.g., /opt/StarWind/VERSION or /opt/StarWind/bin/ starwindd --version). On Windows, check the executable properties or registry under HKLM\SOFTWARE\StarWind.
    Affected if The installed version is exactly 0.2 (the affected version)
  3. Confirm the REST API service is enabled and running
    Check if the StarWind REST API service is active. On Linux: systemctl status starwind or ps aux | grep -i starwind. On Windows: check if the StarWind service is running via services.msc. Also check for port 3261 (default REST API port) listening: netstat -an | grep 3261.
    Affected if The StarWind REST API service is running and listening on network ports
  4. Check for non-root authenticated users
    Review StarWind user configuration. The vulnerability allows any authenticated non-root user to execute commands. Check user accounts configured in StarWind (typically via StarWind Manager or /opt/StarWind/config/users.conf). Determine if any non-root users exist.
    Affected if There is at least one non-root user account configured for StarWind authentication
  5. Inspect the hostname change API endpoint
    If REST API is accessible, the vulnerable endpoint is typically /api/hostname or similar. Review any accessible API documentation or configuration files in the StarWind installation for the hostname change function path. Check configuration files in /opt/StarWind/config/ for API endpoint definitions.
    Affected if The REST API hostname change endpoint exists and is accessible

The environment is affected if StarWind SAN and NAS version 0.2 is installed with the REST API service running and at least one non-root user configured for authentication.

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

Implement strict input validation and sanitization for the hostname parameter before passing to shell commands. If no patch is available, restrict network access to the REST API and consider disabling the hostname change functionality until a fix is deployed.

Fix this in Starwind San \& Nas Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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