LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33653: When performing the derivation shape operation of the SpaceToBatch operator, if there is a value of 0 in th...

When performing the derivation shape operation of the SpaceToBatch operator, if there is a value of 0 in the parameter block_shape 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

CVE-2021-33653 is a MindSpore flaw where certain SpaceToBatch operator input can trigger a division-by-zero exception. The available sources indicate an availability-type failure, not data theft or code execution. Severity and CVSS are not provided, so business urgency depends on whether affected MindSpore versions process untrusted models or workloads.

Executive priority

Treat this as a targeted remediation item, not an emergency, unless affected MindSpore is exposed to untrusted workloads. Prioritize inventory first because the published severity is unknown and no active exploitation is cited.

Technical view

The issue is CWE-369 in the SpaceToBatch operator's derivation shape operation. If a block_shape parameter element is 0, shape derivation can divide by zero and raise an exception. The affected openEuler MindSpore range is >= 0.7.0-beta and < 1.3.0.

Likely exposure

Exposure appears limited to deployments using openEuler-packaged MindSpore versions from 0.7.0-beta before 1.3.0. Risk is higher where users, partners, or automated pipelines can submit model graphs or workloads that exercise MindSpore operators.

Exploitation context

The source bundle does not cite active exploitation, and this CVE is not listed as KEV. The described impact is an exception from invalid operator parameters, suggesting denial-of-service potential if attacker-controlled workloads reach affected MindSpore processing paths.

Researcher notes

Evidence is sparse: no CVSS vector is supplied and the public description focuses on the crash condition. The affected range is clear, but sources do not provide exploit maturity, broad impact analysis, or detailed vendor remediation steps beyond version range context.

Mitigation direction

  • Inventory MindSpore versions across production, research, CI, and container images.
  • Move affected installations outside the >=0.7.0-beta, <1.3.0 range.
  • Check MindSpore and openEuler advisory guidance before choosing exact upgrade targets.
  • Restrict untrusted model or workload submission to affected MindSpore services.
  • Monitor affected services for repeated operator exceptions or crashes.

Validation and detection

  • Confirm whether openEuler MindSpore is installed and record exact versions.
  • Review dependency manifests, images, notebooks, and ML serving environments for MindSpore.
  • Identify services that process third-party or user-submitted models or graphs.
  • Check logs for SpaceToBatch or division-by-zero exceptions.
  • Verify remediated systems no longer run versions before 1.3.0.
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-33653 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.