dbcve.org
QuantastorApplication · Osnexus

CVE-2021-4406

HIGH · 7.2 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to 6.0.0.355 or later.
See remediation →
78/100
Remediation priority · High
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
An authenticated attacker is able to create alerts that trigger a stored XSS attack. POC * go to the alert manager * open the ITSM tab * add a webhook with the URL/service token value ' -h && id | tee /tmp/ttttttddddssss #' (whitespaces are tab characters) * click add * click apply * create a test alert * The test alert will run the command “id | tee /tmp/ttttttddddssss” as root. * after the test alert inspect /tmp/ttttttddddssss it'll contain the ids of the root user.

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

Authenticated command injection vulnerability in the alert manager's webhook/ITSM integration. The URL or service token parameter does not properly sanitize input, allowing an authenticated attacker to inject shell commands that execute with root privileges. The POC demonstrates this by injecting '&& id | tee /tmp/ttttttddddssss' which executes the 'id' command as root.

MitigationImplement strict input validation and sanitization on all webhook/ITSM parameters, using allowlists rather than denylists. Use parameterized APIs or sandboxed execution rather than passing user input to shell commands. Apply the principle of least privilege to limit what the alert execution process can do.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Check Quantastor version
    Run 'qumuloctl version' from the CLI or check the Quantastor web UI dashboard for the installed version number
    Affected if Version is below 6.0.0.355
  2. Locate alert webhook/ITSM configuration
    Navigate to the Quantastor web UI under Alerts > Notification Channels or Alert Manager settings. Identify if any webhook or ITSM integration endpoints are configured and enabled
    Affected if Webhook or ITSM notification channels are actively configured
  3. Inspect webhook URL parameter
    Examine the configured webhook URL field in the alert notification settings. Look for shell metacharacters like &, |, ;, `, or $( ) within the URL value
    Affected if The URL parameter contains shell command injection characters or unexpected syntax
  4. Inspect service token parameter
    Examine the service token or API key field in the webhook/ITSM configuration. Look for injection characters or signs of tampering
    Affected if The token parameter contains shell metacharacters or unusual encoded content
  5. Check for POC artifacts
    Run 'ls -la /tmp/ttttttddddssss' to see if the file from the POC exists, which would indicate exploitation
    Affected if The file /tmp/ttttttddddssss exists on the system

You are affected if running Quantastor version below 6.0.0.355 AND the alert manager webhook/ITSM integration is configured with injectable parameters.

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 and sanitization on all webhook/ITSM parameters, using allowlists rather than denylists. Use parameterized APIs or sandboxed execution rather than passing user input to shell commands. Apply the principle of least privilege to limit what the alert execution process can do.

Recommended fix High confidence

Quantastor 6.0.0.355 or later

  1. Upgrade Quantastor to version 6.0.0.355 or later
  2. After upgrade, verify the fix by attempting to create an alert webhook with command injection characters (e.g., `&&`, `|`, `;`) in the URL/token field
  3. Confirm that the command is treated as a literal string and not executed
  4. If possible, review alert webhook configurations that existed before the upgrade and remove any malicious entries

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

Fix this in Quantastor 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 the upgrade done

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-2021-4406 — 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-4406 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