LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33649: When performing the inference shape operation of the Transpose operator, if the value in the perm element i...

When performing the inference shape operation of the Transpose operator, if the value in the perm element is greater than or equal to the size of the input_shape, it will access data outside of bounds of input_shape which allocated from heap buffers.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

MindSpore had a bounds-checking flaw in the Transpose operator’s shape inference. A malformed permutation value could make the software read past a heap buffer. The public sources do not provide CVSS, business impact, or active exploitation evidence, so urgency depends on whether affected MindSpore versions are used in production or research pipelines.

Executive priority

Prioritize as a targeted dependency remediation if MindSpore is present. The absence of CVSS and exploitation evidence lowers certainty, not necessarily risk. Focus first on systems processing third-party or externally influenced model artifacts.

Technical view

CVE-2021-33649 is a CWE-125 out-of-bounds read in MindSpore versions from 0.7.0-beta before 1.3.0. During Transpose shape inference, a perm element greater than or equal to input_shape size can read outside the allocated heap buffer. Sources do not state exploitability beyond this condition.

Likely exposure

Exposure is limited to deployments using openEuler:mindspore versions >= 0.7.0-beta and < 1.3.0. Risk is more relevant where model graphs or operator definitions may come from less-trusted sources, but the public bundle does not define the attack vector.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit code, or observed attacks. Treat exploit status as unknown, not confirmed exploited.

Researcher notes

The key condition is an unchecked perm index during Transpose shape inference, causing heap out-of-bounds read of input_shape. Public data does not specify crash behavior, disclosure impact, reachability, privileges, or remote attack requirements. Avoid assuming more than CWE-125 without vendor details.

Mitigation direction

  • Inventory MindSpore versions across production, CI, research, and container images.
  • Move affected MindSpore installations outside the >=0.7.0-beta and <1.3.0 range.
  • Check the MindSpore security advisory for vendor-confirmed fixed versions or workarounds.
  • Restrict use of untrusted model artifacts until affected systems are remediated.
  • Prioritize remediation where MindSpore handles externally supplied models or workloads.

Validation and detection

  • Confirm installed MindSpore versions are not within the affected range.
  • Review dependency manifests and container layers for bundled MindSpore copies.
  • Identify workflows that run Transpose shape inference on imported models.
  • Verify remediation against the vendor advisory before closing tickets.
  • Record systems where exposure cannot be determined from available evidence.
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-125: 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-33649 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-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.