Code execution via unsafe dill deserialization
Published Mar 14, 2024 · Updated Aug 29, 2024
Unsafe deserialization in LinkedIn Greykite 1.0.0 allows attackers to execute arbitrary code when an application loads a crafted result directory. The load_obj function recursively passes .type and .pkl files from the supplied directory to dill.load without restricting the classes or reduction callables they encode. Exploitation requires a consuming application to accept attacker-controlled files and invoke this library helper; Greykite itself exposes no upload service.
Summary
What happened
Unsafe deserialization in LinkedIn Greykite 1.0.0 allows attackers to execute arbitrary code when an application loads a crafted result directory. The load_obj function recursively passes .type and .pkl files from the supplied directory to dill.load without restricting the classes or reduction callables they encode. Exploitation requires a consuming application to accept attacker-controlled files and invoke this library helper; Greykite itself exposes no upload service.
The record
- CVE
- CVE-2024-28425
- Published
- Mar 14, 2024
- Updated
- Aug 29, 2024
- Vendor
- Product
- Greykite
- Classifications
- CWE-434, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo