CVE-2024-10095: Progress UI for WPF format provider unsafe deserialization vulnerability
First published: Mon Dec 16 2024(Updated: )
In Progress Telerik UI for WPF versions prior to 2024 Q4 (2024.4.1213), a code execution attack is possible through an insecure deserialization vulnerability.
Credit: security@progress.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Telerik UI for WPF | <24.4.1213 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-10095?
CVE-2024-10095 has a high severity rating due to its potential to allow remote code execution.
How do I fix CVE-2024-10095?
To mitigate CVE-2024-10095, upgrade to Telerik UI for WPF version 2024 Q4 (2024.4.1213) or later.
What causes the vulnerability CVE-2024-10095?
CVE-2024-10095 is caused by insecure deserialization, allowing an attacker to execute arbitrary code.
Which versions of Telerik UI for WPF are affected by CVE-2024-10095?
Telerik UI for WPF versions prior to 2024 Q4 (2024.4.1213) are affected by CVE-2024-10095.
Is CVE-2024-10095 being actively exploited?
As of now, there are no confirmed reports of active exploitation of CVE-2024-10095, but it poses a significant risk.
- agent/weakness
- agent/title
- agent/references
- agent/first-publish-date
- agent/description
- agent/type
- agent/author
- agent/event
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/trending
- agent/tags
- agent/source
- vendor/telerik
- canonical/telerik ui for wpf