Storage ManagerApplication · Qsan

CVE-2021-32506

MEDIUM · 6.5 CVSS v3.1 Published 2021-07-07
Fix available
A fix is available. Upgrade to 3.3.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Absolute Path Traversal vulnerability in GetImage in QSAN Storage Manager allows remote authenticated attackers download arbitrary files via the Url path parameter. 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

Absolute path traversal vulnerability in QSAN Storage Manager's GetImage function allows authenticated remote attackers to download arbitrary files by manipulating the URL path parameter. The vulnerability enables reading sensitive system files due to insufficient input validation on the path parameter.

MitigationUpgrade QSAN Storage Manager to version 3.3.3 or later to remediate the path traversal vulnerability. Since this requires authenticated access, also review and rotate credentials that may have been compromised.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if QSAN Storage Manager is installed
    Locate QSAN Storage Manager in your environment - typically runs as a web service on port 8080 or 8443. Check running services or installed applications for 'QSAN' or 'Storage Manager' processes.
    Affected if QSAN Storage Manager software is present in the environment
  2. Determine the installed version
    Access the web management interface and check the About/Help section, or check the installed software package version. Compare the version number against the affected range: versions prior to 3.3.3 are vulnerable.
    Affected if Installed version is lower than 3.3.3
  3. Verify the GetImage function is accessible
    Attempt to access the GetImage endpoint via the web interface. The vulnerability exists in the GetImage function which handles image retrieval requests.
    Affected if The GetImage function endpoint is reachable and accepts URL path parameters
  4. Confirm authentication status
    Review the authentication configuration for the QSAN Storage Manager web interface. The vulnerability requires authenticated access, so determine whether authentication is enforced, disabled, or using default credentials.
    Affected if Authentication is disabled, weak, or using default credentials allowing unauthorized access to the GetImage function
  5. Check for suspicious access logs
    Review web server access logs for requests to the GetImage endpoint with unusual path traversal patterns (e.g., requests containing '../' or absolute paths like '/etc/passwd').

The environment is affected if QSAN Storage Manager version is below 3.3.3 AND the GetImage web function is accessible with valid credentials.

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
Upgrade available Upgrade to 3.3.3 or later
Fixed in 3.3.3
Interim mitigation

Upgrade QSAN Storage Manager to version 3.3.3 or later to remediate the path traversal vulnerability. Since this requires authenticated access, also review and rotate credentials that may have been compromised.

Fix this in Storage Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32506 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