dbcve.org
MxnetApplication · Apache

CVE-2022-24294

HIGH · 7.5 CVSS v3.1 Published 2022-07-24
Fix available
A fix is available. Upgrade to 1.9.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 regular expression used in Apache MXNet (incubating) is vulnerable to a potential denial-of-service by excessive resource consumption. The bug could be exploited when loading a model in Apache MXNet that has a specially crafted operator name that would cause the regular expression evaluation to use excessive resources to attempt a match. This issue affects Apache MXNet versions prior to 1.9.1.

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 · high confidence

Apache MXNet contains a vulnerable regular expression used during model loading. When loading a model with a specially crafted operator name, the regex evaluation enters a pathological backtracking scenario, consuming excessive CPU resources and causing denial of service. This is a classic ReDoS (Regular Expression Denial of Service) vulnerability.

MitigationUpgrade Apache MXNet to version 1.9.1 or later. Until then, avoid loading models from untrusted sources as they may contain specially crafted operator names that trigger the vulnerable regex.

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
MxnetApplication
Affected:< 1.9.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed MXNet version
    Run 'pip show mxnet' or 'python -c "import mxnet; print(mxnet.__version__)"' to retrieve the installed Apache MXNet version number
    Affected if The installed version is lower than 1.9.1 (e.g., 1.9.0, 1.8.0, 1.7.0, etc.)
  2. Confirm model loading capability is present
    Check if the MXNet installation includes model loading modules by verifying 'from mxnet import model' or 'import mxnet.io' executes without error
    Affected if MXNet model loading modules are available in the environment and the version is vulnerable
  3. Verify models from external sources are processed
    Inspect any application code, scripts, or pipelines that call mxnet.model.load() or related model deserialization functions to determine if untrusted model files are processed
    Affected if The environment loads model files (JSON/params) from sources that could contain specially crafted operator names

You are affected if Apache MXNet version is below 1.9.1 AND your environment loads model files, as the vulnerable regex in model loading can be triggered by specially crafted operator names.

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.

dbcve · scoped
Upgrade available Upgrade to 1.9.1 or later
Fixed in 1.9.1
Interim mitigation

Upgrade Apache MXNet to version 1.9.1 or later. Until then, avoid loading models from untrusted sources as they may contain specially crafted operator names that trigger the vulnerable regex.

Recommended fix High confidence

1.9.1

  1. 1. Identify the current MXNet version installed in your environment using pip show mxnet or conda list mxnet
  2. 2. Upgrade MXNet to version 1.9.1 or later using pip: pip install --upgrade mxnet>=1.9.1
  3. 3. Alternatively, if using conda: conda install mxnet=1.9.1
  4. 4. Verify the upgrade was successful by running: pip show mxnet and confirming the version number
  5. 5. Test that model loading functionality works correctly with your existing models
Caveat Review the MXNet 1.9.1 release notes for any API changes or deprecations that may affect existing code

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mxnet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24294 — 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-2022-24294 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