CVE-2024-0140
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 · uneditedNVIDIA RAPIDS contains a vulnerability in cuDF and cuML, where a user could cause a deserialization of untrusted data issue. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure.
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 confidenceNVIDIA RAPIDS cuDF and cuML libraries contain a deserialization vulnerability where processing untrusted data can lead to arbitrary code execution, data tampering, denial of service, or information disclosure. This class of flaw typically stems from unsafe object deserialization without proper validation, allowing attackers to manipulate the deserialization process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if cuDF is installedRun 'pip list' or 'conda list' and look for 'cudf' in the output, or import in Python with 'import cudf; print(cudf.__version__)'Affected if cuDF is installed and the version is lower than the patched release mentioned in NVIDIA's security advisory for CVE-2024-0140
-
Identify if cuML is installedRun 'pip list' or 'conda list' and look for 'cuml' in the output, or import in Python with 'import cuml; print(cuml.__version__)'Affected if cuML is installed and the version is lower than the patched release mentioned in NVIDIA's security advisory for CVE-2024-0140
-
Verify if untrusted data deserialization is occurringSearch codebases for usage of pickle, joblib, or similar deserialization functions on data from untrusted sources, especially involving cuDF DataFrames or cuML modelsAffected if Code processes untrusted serialized data through cuDF or cuML without validation
-
Check for exposed API endpoints or services processing external inputAudit any APIs, web services, or data pipelines that accept external serialized objects and pass them to cuDF or cuML functionsAffected if External untrusted input is directly deserialized and processed by RAPIDS libraries
Environment is affected if either cuDF or cuML is installed with a version below the patched release AND the system processes untrusted serialized data through these libraries.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement input validation and use safe deserialization patterns; consult NVIDIA's security advisories for specific patched versions of cuDF and cuML, and upgrade to the latest secure release.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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