dbcve.org
MindsporeApplication

CVE-2023-2970

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability classified as problematic was found in MindSpore 2.0.0-alpha/2.0.0-rc1. This vulnerability affects the function JsonHelper::UpdateArray of the file mindspore/ccsrc/minddata/dataset/util/json_helper.cc. The manipulation leads to memory corruption. The name of the patch is 30f4729ea2c01e1ed437ba92a81e2fc098d608a9. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-230176.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A memory corruption vulnerability exists in MindSpore's JSON utility (mindspore/ccsrc/minddata/dataset/util/json_helper.cc) in the JsonHelper::UpdateArray function. The flaw allows manipulation that leads to improper memory handling during array updates in the data pipeline component, potentially allowing an attacker to cause undefined behavior or crash the application.

MitigationApply the vendor-supplied patch (commit 30f4729ea2c01e1ed437ba92a81e2fc098d608a9) to MindSpore 2.0.0-alpha/2.0.0-rc1. If immediate patching is not possible, restrict access to datasets or configurations that trigger the affected JSON helper code path.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MindsporeApplication
Affected:= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MindSpore version
    Run 'python -c "import mindspore; print(mindspore.__version__)"' or 'pip show mindspore' to retrieve the installed version
    Affected if The version is 2.0.0, 2.0.0-alpha, or 2.0.0-rc1
  2. Identify JSON data pipeline usage
    Search project code for imports of mindspore.dataset and usage of JSON-based dataset configurations (e.g., MINDDataset, JsonDataset, or custom JSON files passed to data pipeline APIs)
    Affected if The application loads JSON files or configurations into MindSpore's data pipeline that would invoke JsonHelper::UpdateArray
  3. Locate vulnerable source file
    Check if the file mindspore/ccsrc/minddata/dataset/util/json_helper.cc exists in the MindSpore installation or source tree, or search for 'JsonHelper::UpdateArray' in compiled binaries
    Affected if The vulnerable source file is present and the UpdateArray function is accessible in the build
  4. Verify data pipeline component is loaded
    Run the data pipeline with JSON input and monitor for crashes or undefined behavior using debugging tools (e.g., AddressSanitizer, Valgrind) or by inspecting core dumps if the process terminates unexpectedly
    Affected if The application crashes or exhibits undefined behavior when processing JSON array updates in the data pipeline
  5. Inspect JSON input patterns
    Review all JSON configuration files and data inputs passed to MindSpore data pipeline APIs for array modification operations that would trigger the UpdateArray code path
    Affected if JSON inputs contain array update operations processed by the vulnerable function

You are affected if MindSpore version 2.0.0 (including alpha/rc1) is installed AND your data pipeline processes JSON configurations that invoke the JsonHelper::UpdateArray function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch (commit 30f4729ea2c01e1ed437ba92a81e2fc098d608a9) to MindSpore 2.0.0-alpha/2.0.0-rc1. If immediate patching is not possible, restrict access to datasets or configurations that trigger the affected JSON helper code path.

Fix this in Mindspore Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2970 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data