dbcve.org
QuantastorApplication · Osnexus

CVE-2021-42082

HIGH · 7.8 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to 6.0.0.355 or later.
See remediation →
80/100
Remediation priority · High
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
Local users are able to execute scripts under root privileges. POC On the local host run the following command: curl 'localhost:8154/qstor/qs_upgrade.py?taskId=1&a=;`whoami`'

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 qs_upgrade.py allows arbitrary command execution via the 'a' parameter in the query string. The injected commands execute with root privileges, enabling full system compromise.

MitigationImplement strict input validation to prevent command injection, avoid using user input in shell commands, and run the web service with least privilege rather than root.

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
QuantastorApplication
Affected:< 6.0.0.355

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

CVSS:3.1/AV:L/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. Confirm Quantastor installation
    Identify if Osnexus Quantastor storage management software is installed on the system. Look for Quantastor installation directories, services, or web interface listening on common ports (such as 443 or 8080).
    Affected if Quantastor is installed and running on the system
  2. Check Quantastor version
    Locate and read the installed Quantastor version. This is typically accessible via the web management interface, command-line tool (qsコマンド), or version file in the installation directory. Compare the version number to 6.0.0.355.
    Affected if Installed version is lower than 6.0.0.355 (e.g., 6.0.0.300, 5.x.x, etc.)
  3. Verify qs_upgrade.py is accessible
    Check if the qs_upgrade.py component exists in the web application's upgrade or admin module. This is typically accessible via the Quantastor web interface path (often under /upgrade/ or similar admin endpoints).
    Affected if The qs_upgrade.py script is present and accessible via the web interface
  4. Confirm web service runs as root
    Examine the process running the Quantastor web service to determine the execution privilege level. This can be done by checking process ownership or service configuration.
    Affected if The Quantastor web service process runs with root or administrator privileges

The environment is affected if Quantastor is installed with a version below 6.0.0.355, the qs_upgrade.py endpoint is accessible, and the web service runs with root privileges, allowing command injection through the 'a' query parameter.

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.0.0.355 or later
Fixed in 6.0.0.355
Interim mitigation

Implement strict input validation to prevent command injection, avoid using user input in shell commands, and run the web service with least privilege rather than root.

Recommended fix High confidence

Quantastor version 6.0.0.355 or later

  1. 1. Back up all critical data and configurations on the Quantastor system before proceeding with the upgrade.
  2. 2. Download the Quantastor version 6.0.0.355 or later from the official vendor (osnexus.com).
  3. 3. Log into the Quantastor administrative interface or access the system via secure shell (SSH).
  4. 4. Apply the upgrade following the vendor's documented upgrade procedure for Quantastor.
  5. 5. Verify the upgrade was successful by checking the Quantastor version (should be >= 6.0.0.355).
  6. 6. Confirm the vulnerability is remediated by testing that command injection through the qs_upgrade.py endpoint is no longer possible.
Caveat Review release notes for any configuration or feature changes between your current version and 6.0.0.355 to ensure compatibility with your environment.

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

Fix this in Quantastor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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