CVE-2024-28425
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 · uneditedgreykite v1.0.0 was discovered to contain an arbitrary file upload vulnerability in the load_obj function at /templates/pickle_utils.py. This vulnerability allows attackers to execute arbitrary code via uploading a crafted file.
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 confidencegreykite v1.0.0 contains an arbitrary file upload vulnerability in the load_obj function within /templates/pickle_utils.py. The function appears to insecurely deserialize untrusted pickle files, allowing attackers to upload crafted files and achieve arbitrary code execution on the target system.
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= 1.0.0CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 greykite installation versionRun 'pip show greykite' or check your requirements.txt for the installed version of the greykite packageAffected if The installed version is exactly 1.0.0 (note: only this specific version is listed as affected)
-
Locate the vulnerable pickle_utils.py fileFind the file templates/pickle_utils.py within the greykite package installation directory (typically in site-packages/greykite)Affected if The file exists and contains a function named load_obj that performs pickle.load() operations
-
Inspect the load_obj function for insecure deserializationOpen pickle_utils.py and examine the load_obj function implementation for unpickled data loaded from file input without validationAffected if The function uses pickle.load() without restricted unpicklers, custom finders, or input validation
-
Check if your application code calls load_obj on untrusted inputSearch your codebase for calls to load_obj or greykite.templates.pickle_utils.load_obj that process files from user-uploaded sourcesAffected if Your code passes external/pickle files to load_obj without sanitization
You are affected if you have greykite v1.0.0 installed AND your application uses the load_obj function to deserialize pickle files from untrusted sources.
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 dataReplace insecure pickle deserialization with safe alternatives (e.g., JSON, msgpack) or implement strict allowlist validation on file inputs before loading. If pickle is required, use restricted unpicklers with a custom finder to prevent arbitrary code execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28425 — 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-28425 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