CVE-2024-45857
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 · uneditedDeserialization of untrusted data can occur in versions 2.4.0 or newer of the Cleanlab project, enabling a maliciously crafted datalab.pkl file to run arbitrary code on an end user’s system when the data directory is loaded.
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 confidenceCleanlab versions 2.4.0+ contain an insecure deserialization vulnerability where loading a maliciously crafted datalab.pkl file allows arbitrary code execution. This occurs because the application deserializes untrusted pickle data without validation, enabling remote code execution when victims load compromised data directories.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Confirm Cleanlab installation and versionRun 'pip show cleanlab' or 'pip list | grep cleanlab' to identify the installed versionAffected if The installed version is 2.4.0 or higher
-
Identify pickle file loading in your codeSearch your codebase for patterns like 'pickle.load', 'pickle.loads', 'pd.read_pickle', or any references to 'datalab.pkl'Affected if Your code loads .pkl files, particularly datalab.pkl, from untrusted sources
-
Check for pickle security measuresInspect the code that loads pickle files to see if it uses a restricted Unpickler with allowed_classes parameter, or implements custom validation before deserializationAffected if The pickle loading code does not use a restricted Unpickler and performs no validation on the pickle data before loading
-
Verify source of pickle filesReview data workflows to determine if .pkl files are received from external sources, network endpoints, or user uploads that could be tampered withAffected if The application loads pickle files from untrusted or external sources without verification
You are affected if Cleanlab version 2.4.0 or higher is installed AND your application loads .pkl files (especially datalab.pkl) without using a restricted Unpickler or validating the data source.
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 dataUpgrade to a patched version when available. Until then, validate the source of all .pkl files before loading, implement safe deserialization using pickle's restricted unpickler (e.g., restricted Unpickler with allowed_classes), or migrate to safer serialization formats like JSON.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45857 — 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-45857 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