CVE-2024-37064
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 · uneditedDeseriliazation of untrusted data can occur in versions 3.7.0 or newer of Ydata's ydata-profiling open-source library, enabling a maliciously crafted dataset to run arbitrary code on an end user's system when 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 · moderate confidenceA deserialization vulnerability in ydata-profiling versions 3.7.0 and newer allows arbitrary code execution when loading a maliciously crafted dataset. The vulnerability stems from unsafe deserialization of untrusted data within the profiling library.
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.
-
Identify if ydata-profiling is installedRun 'pip show ydata-profiling' or check your project's dependencies (requirements.txt, pyproject.toml, or similar) for the ydata-profiling packageAffected if The package is not present in your environment
-
Determine the installed versionRun 'pip show ydata-profiling' and note the Version field, or check your lock file for the exact version numberAffected if The version is 3.7.0 or higher (any version from 3.7.0 onward)
-
Identify data input sourcesReview your code to determine what datasets are passed to ydata-profiling's profiling functions (e.g., pandas_profiling, ProfileReport)Affected if Datasets from untrusted or external sources are loaded into the library
You are affected if ydata-profiling version 3.7.0 or higher is installed AND you load datasets from untrusted or external sources into the profiling library.
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.
dbcve · scopedUsers should avoid loading datasets from untrusted sources and update to patched versions of ydata-profiling once available. Consider validating or sanitizing any dataset before processing.
Latest available version of ydata-profiling (newer than 3.7.0)
- 1. Identify the current installed version of ydata-profiling by running: pip show ydata-profiling or pip list | grep ydata-profiling
- 2. Upgrade to the latest version of ydata-profiling using: pip install --upgrade ydata-profiling
- 3. Verify the upgrade was successful by checking the new version: pip show ydata-profiling
- 4. Test that your existing code and workflows still function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37064 — 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-37064 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