LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32532: QSAN XEVO - Path Traversal

Path traversal vulnerability in back-end analysis function in QSAN XEVO allows remote attackers to download arbitrary files without permissions. The referred vulnerability has been solved with the updated version of QSAN XEVO v2.1.0.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-32532 is a path traversal flaw in QSAN XEVO. A remote attacker could download arbitrary files without permission, creating a serious confidentiality risk. The source says the issue is fixed in QSAN XEVO v2.1.0.

Executive priority

Prioritize remediation for any reachable QSAN XEVO deployment because the issue can expose sensitive files without credentials. Business urgency is highest where storage management systems are internet-facing or accessible from broad internal networks.

Technical view

The vulnerability is CWE-22 path traversal in a QSAN XEVO back-end analysis function. CVSS 3.1 is 7.5, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality impact only. Affected versions are not specified beyond QSAN XEVO before the named fixed release.

Likely exposure

Exposure is most likely where QSAN XEVO is deployed and reachable over a network, especially from untrusted networks. The source bundle does not identify specific vulnerable versions, CPEs, or deployment configurations.

Exploitation context

The sources describe remote unauthenticated file download, but do not provide evidence of active exploitation. CISA KEV status is false in the supplied bundle, so treat exploitation as plausible but not confirmed.

Researcher notes

Evidence is limited: affected versions are unspecified, and the only fix detail is QSAN XEVO v2.1.0. Do not assume broader QSAN product impact. Focus validation on version confirmation, exposure mapping, and log review rather than exploit reproduction.

Mitigation direction

  • Upgrade QSAN XEVO to the vendor-stated fixed version, v2.1.0.
  • Inventory all QSAN XEVO deployments and record current versions.
  • Restrict network access to XEVO administrative or back-end interfaces.
  • Review QSAN or TWCERT guidance for any additional vendor instructions.
  • Monitor logs for unusual file access or download activity.

Validation and detection

  • Confirm each QSAN XEVO instance is running v2.1.0 or the vendor-approved fixed release.
  • Verify no QSAN XEVO interfaces are exposed to untrusted networks unnecessarily.
  • Review application and access logs for suspicious file-download patterns.
  • Confirm vulnerability records do not list this CVE as KEV-exploited.
  • Document any remaining instances with unspecified or unverified versions.
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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-32532 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-32532Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.