LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33652: When the Reduce operator run operation is executed, if there is a value of 0 in the parameter axis_sizes el...

When the Reduce operator run operation is executed, if there is a value of 0 in the parameter axis_sizes element, it will cause a division by 0 exception.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a division-by-zero crash condition in MindSpore's Reduce operator. If affected versions process a Reduce operation where an axis_sizes value is 0, the operation can raise an exception. The available sources do not provide CVSS scoring, exploit evidence, or detailed business impact.

Executive priority

Treat this as a targeted reliability risk for affected MindSpore deployments. Prioritize remediation where MindSpore processes untrusted workloads or supports production AI services. Overall urgency is constrained by missing CVSS, unclear reachability, and no cited exploitation evidence.

Technical view

CVE-2021-33652 is classified as CWE-369. Affected openEuler:mindspore versions are listed as >= 0.7.0-beta and < 1.3.0. The vulnerable condition occurs during Reduce operator execution when an axis_sizes element is 0, causing division by zero.

Likely exposure

Exposure appears limited to environments running affected MindSpore versions and executing Reduce operations with vulnerable axis_sizes input. The sources do not state whether this is reachable remotely, through model files, APIs, or only local code paths.

Exploitation context

The source bundle does not show active exploitation, and this CVE is not listed as KEV. Available evidence supports a crash or exception condition, not code execution. Practical exploitability depends on whether untrusted inputs can influence Reduce operator parameters.

Researcher notes

The key research gap is reachability. The public description identifies the faulty condition but not attack vector, privileges, availability impact scope, or fixed commit. Validate only in controlled environments and avoid assuming remote exploitability without additional vendor evidence.

Mitigation direction

  • Inventory MindSpore deployments and identify versions from 0.7.0-beta through before 1.3.0.
  • Review MindSpore MSSA-2021-003 for vendor remediation guidance.
  • Prioritize upgrading systems out of the affected version range.
  • Restrict untrusted model or operator inputs where Reduce parameters are externally influenced.
  • Monitor vendor advisories for any updated severity or patch details.

Validation and detection

  • Confirm deployed MindSpore package versions against the affected range.
  • Review workloads for use of the Reduce operator.
  • Check whether untrusted input can influence axis_sizes values.
  • Verify remediation by confirming systems run outside the affected range.
  • Document any compensating controls for exposed AI or ML processing services.
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 · low confidence lookup

CWE-369: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2021-33652 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aopenEuler:mindspore>= 0.7.0-beta, < 1.3.0Listed
Weakness

CWE details

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

CWE-369 · source CWE mapping

Divide By Zero

Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.