dbcve.org
Storage ManagerApplication · Qsan

CVE-2021-32513

CRITICAL · 9.8 CVSS v3.1 Published 2021-07-07
Fix available
A fix is available. Upgrade to 3.3.3 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
QsanTorture in QSAN Storage Manager does not filter special parameters properly that allows remote unauthenticated attackers to inject and execute arbitrary commands. The referred vulnerability has been solved with the updated version of QSAN Storage Manager v3.3.3.

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

QsanTorture in QSAN Storage Manager fails to properly filter special parameters, allowing remote unauthenticated attackers to inject and execute arbitrary commands. This is a pre-authentication command injection vulnerability with critical severity due to the ability to execute arbitrary commands without credentials.

MitigationUpdate QSAN Storage Manager to version v3.3.3 or later to remediate the command injection vulnerability. As this is a critical, easily exploitable flaw, prioritize patching immediately.

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
Storage ManagerApplication
Affected:< 3.3.3

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 Storage Manager is installed
    Locate the QSAN Storage Manager software on the system. Common installation paths include /opt/qsan or C:\Program Files\QSAN. Check for running processes named 'StorageManager' or 'QsanTorture' using system process lists.
    Affected if QSAN Storage Manager software is found running on the system
  2. Determine installed version of QSAN Storage Manager
    Check the installed version through the software's web interface (usually accessible on port 8081 or 443), or by examining version files in the installation directory. The version is typically displayed in the web UI header or in a 'version.ini' file within the installation folder.
    Affected if The installed version is lower than 3.3.3 (e.g., 3.3.2, 3.3.1, 3.2.x, etc.)
  3. Verify QsanTorture component is accessible
    Confirm the QsanTorture web interface is reachable. This is typically accessed via HTTP/HTTPS on the management port. Check network listeners using netstat or similar tools to see if port 8081 or the configured management port is open and listening.
    Affected if The QsanTorture interface is network-accessible without authentication (the vulnerability is pre-authentication)
  4. Confirm no authentication is required for the management interface
    Attempt to access the QSAN Storage Manager login page or QsanTorture endpoint from a non-authenticated state. Observe if the application returns a login prompt or allows access to the command injection endpoint without credentials.
    Affected if The interface allows access or interaction without requiring valid credentials

The environment is affected if QSAN Storage Manager version is below 3.3.3 AND the QsanTorture management interface is network-accessible without 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.

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

Update QSAN Storage Manager to version v3.3.3 or later to remediate the command injection vulnerability. As this is a critical, easily exploitable flaw, prioritize patching immediately.

Recommended fix High confidence

QSAN Storage Manager v3.3.3

  1. Download QSAN Storage Manager version 3.3.3 from the official QSAN vendor website
  2. Follow QSAN's standard upgrade procedure to install version 3.3.3
  3. Verify the installation completed successfully and the service is running

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

Fix this in Storage Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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