dbcve.org
SanosApplication · Qsan

CVE-2021-32534

CRITICAL · 9.8 CVSS v3.1 Published 2021-07-07
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
QSAN SANOS factory reset function does not filter special parameters. Remote attackers can use this vulnerability to inject and execute arbitrary commands without permissions. The referred vulnerability has been solved with the updated version of QSAN SANOS v2.1.0.

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 QSAN SANOS factory reset function lacks proper input sanitization, allowing remote unauthenticated attackers to inject and execute arbitrary OS commands. This is a command injection vulnerability in the factory reset feature that can be exploited remotely without any authentication.

MitigationUpgrade to QSAN SANOS v2.1.0 or later. If immediate patching is not feasible, restrict network access to the SAN management interface to reduce attack surface.

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
SanosApplication
Affected:< 2.1.0

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
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 checks

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

  1. Confirm QSAN SANOS product is in use
    Identify the storage system product name through the management interface, system information page, or boot-up screen. QSAN SANOS is the operating system running on QSAN storage arrays.
    Affected if The product is a QSAN storage device running SANOS firmware.
  2. Determine installed SANOS version
    Access the SANOS management web interface and navigate to the system information or about section to retrieve the firmware version number. Compare this version against the affected range.
    Affected if The installed SANOS version is any release prior to version 2.1.0.
  3. Verify factory reset endpoint is accessible
    Check if the factory reset functionality is reachable through the SANOS web interface or API without authentication. This is typically found in system maintenance or reset settings.
    Affected if The factory reset feature can be accessed remotely without requiring login credentials.
  4. Assess network exposure of SAN management interface
    Determine if the QSAN management interface is directly accessible from untrusted networks. Check firewall rules, VLAN configuration, and access control lists protecting the SAN management port.
    Affected if The SANOS management interface is exposed to the internet or untrusted internal networks without network-level access controls.

The environment is affected if QSAN SANOS version is below 2.1.0 AND the management interface with factory reset functionality is accessible from the network where attackers could reach it.

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 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Upgrade to QSAN SANOS v2.1.0 or later. If immediate patching is not feasible, restrict network access to the SAN management interface to reduce attack surface.

Recommended fix High confidence

QSAN SANOS v2.1.0

  1. 1. Identify the current QSAN SANOS version by accessing the SAN management interface or running the appropriate version command.
  2. 2. Download the QSAN SANOS v2.1.0 update package from the official QSAN support website or trusted distribution channel.
  3. 3. Access the SAN management console with administrative credentials.
  4. 4. Navigate to the firmware upgrade or system update section.
  5. 5. Upload and apply the SANOS v2.1.0 update package following the vendor's documented upgrade procedure.
  6. 6. After the upgrade completes, verify the system is operational and confirm the new version is 2.1.0.
  7. 7. Test the factory reset function to ensure it now properly filters special parameters and the vulnerability is remediated.

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

Fix this in Sanos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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