LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32530: QSAN XEVO - Command Injection Following via Array function

OS command injection vulnerability in Array function in QSAN XEVO allows remote unauthenticated attackers to execute arbitrary commands via status parameter. The referred vulnerability has been solved with the updated version of QSAN XEVO v2.1.0.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

QSAN XEVO has a critical flaw that could let an unauthenticated remote attacker run operating system commands through a vulnerable Array function parameter. That can mean full compromise of the affected storage management environment. The provided sources say QSAN resolved it in XEVO v2.1.0.

Executive priority

Treat as urgent for any QSAN XEVO environment. Remote unauthenticated command execution against storage management software can create direct operational, data confidentiality, and recovery risks. Prioritize version verification and upgrade.

Technical view

CVE-2021-32530 is a CWE-78 OS command injection issue in QSAN XEVO. The vulnerability is reachable over the network with low complexity, no privileges, and no user interaction, via the status parameter in the Array function. CVSS 3.1 is 9.8 critical.

Likely exposure

Exposure is limited to QSAN XEVO deployments, especially systems running versions before the vendor-fixed XEVO v2.1.0 or systems where version status is unknown. Internet-facing or broadly reachable management interfaces would materially increase business risk.

Exploitation context

The provided bundle does not show active exploitation, and KEV is false. However, the vulnerability characteristics are severe: remote, unauthenticated command execution with high confidentiality, integrity, and availability impact.

Researcher notes

Affected versions are not precisely enumerated in the supplied sources; they only state the issue was solved in XEVO v2.1.0. Do not assume exploitation status beyond the absence of KEV listing and lack of provided exploitation evidence.

Mitigation direction

  • Upgrade QSAN XEVO to v2.1.0 or vendor-recommended newer release.
  • Confirm vendor guidance for any additional required remediation.
  • Restrict XEVO management access to trusted administrative networks.
  • Remove direct internet exposure for affected XEVO interfaces.
  • Monitor for suspicious access to XEVO management endpoints.

Validation and detection

  • Inventory all QSAN XEVO instances and record their software versions.
  • Verify whether each instance is running v2.1.0 or later.
  • Identify any XEVO interfaces reachable from untrusted networks.
  • Review access logs for unusual Array function or status parameter activity.
  • Document remediation status for each affected storage system.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32530 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-32530Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
QSANXEVOunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.