Local code execution via PersistenceFramework deserialization
Published Dec 16, 2024 · Updated Dec 16, 2024
Insecure deserialization in Progress Telerik UI for WPF before 2024.4.1213 allows local users to execute code through PersistenceFramework. The PersistenceFramework component deserializes untrusted persisted application state in a manner that permits code execution. Exposure requires a Windows application built with the affected library to use PersistenceFramework; applications that do not use that component are unaffected.
Summary
What happened
Insecure deserialization in Progress Telerik UI for WPF before 2024.4.1213 allows local users to execute code through PersistenceFramework. The PersistenceFramework component deserializes untrusted persisted application state in a manner that permits code execution. Exposure requires a Windows application built with the affected library to use PersistenceFramework; applications that do not use that component are unaffected.
The record
- CVE
- CVE-2024-10095
- Published
- Dec 16, 2024
- Updated
- Dec 16, 2024
- Vendor
- Progress Software Corporation
- Product
- Telerik UI for WPF
- Classifications
- CWE-502, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 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=0 <2024.4.1213
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