CVE-2024-37062
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 3.7.0 or newer of Ydata's ydata-profiling open-source library, enabling a malicously crafted report 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 exists in ydata-profiling versions 3.7.0 and newer where loading a maliciously crafted report file can trigger arbitrary code execution on the victim's system. The vulnerability stems from insecure handling of untrusted serialized data within the report loading mechanism.
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.
-
Check if ydata-profiling is installedRun 'pip show ydata-profiling' or 'pip list | grep ydata-profiling' to see if the package is present in your environmentAffected if The package is installed and the version is 3.7.0 or newer
-
Verify the installed version numberLook for the 'Version:' field in the pip show output and compare it to 3.7.0 using a version comparisonAffected if The installed version is 3.7.0, 3.7.1, 3.8.0, or any version 3.7.0 or newer
-
Identify code that loads report filesSearch your codebase for calls to functions that load ydata-profiling reports, such as 'ProfileReport' with file input or deserialization methods reading previously generated report filesAffected if Code loads report files generated by ydata-profiling, particularly from untrusted or external sources
-
Inspect report file sourcesReview log files, download directories, or user upload paths where ydata-profiling report files (.html or serialized files) may be loadedAffected if Your application loads report files from untrusted or unknown sources without validation
-
Check for serialized data handlingExamine how report files are processed - look for pickle, joblib, or similar deserialization operations on report dataAffected if The report loading mechanism deserializes data without validation, allowing untrusted serialized content to be processed
You are affected if ydata-profiling version 3.7.0 or newer is installed AND your system loads report files, especially from untrusted sources, without validation.
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 dataAvoid loading ydata-profiling reports from untrusted or unknown sources. Update to patched versions of the library when released and implement input validation on report files before deserialization.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37062 — 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-37062 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