CVE-2024-10095
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 · uneditedIn Progress Telerik UI for WPF versions prior to 2024 Q4 (2024.4.1213), a code execution attack is possible through an insecure deserialization vulnerability.
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 confidenceProgress Telerik UI for WPF contains an insecure deserialization vulnerability in versions prior to 2024 Q4 (2024.4.1213). An attacker can exploit this flaw to achieve remote code execution by sending specially crafted serialized data to vulnerable deserialization endpoints.
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< 24.4.1213CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Telerik UI for WPF installationSearch for Telerik.UI.for.WPF assembly in the application's bin directory, or check the project references (.csproj) or packages.config for Telerik packages. Also check GAC or installed assemblies on the system.Affected if Telerik UI for WPF is present in the environment
-
Determine installed versionLocate the Telerik.UI.for.WPF.dll file and check its version property, or inspect the package reference version in the project file or NuGet packages.config. The version format appears as major.minor.build (e.g., 24.3.x.x).Affected if The version number is lower than 24.4.1213
-
Check for deserialization usageSearch codebase for usage of BinaryFormatter, ObjectStateFormatter, LosFormatter, or any custom ISerializationSurrogate that deserializes data from untrusted sources, especially related to Telerik components. Review any endpoints or handlers that accept serialized data.Affected if The application deserializes data from external or untrusted sources using .NET serialization mechanisms
-
Review configuration for vulnerable handlersCheck web.config or app.config for HttpHandlers or modules that process serialized data, particularly any Telerik-related handlers. Also inspect any .ashx, .asmx, or WCF endpoints that may handle serialized objects.Affected if Configured handlers accept or process serialized .NET objects from clients
The environment is affected if Telerik UI for WPF is installed with a version lower than 24.4.1213 AND the application deserializes data from untrusted sources using .NET serialization mechanisms.
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.
dbcve · scoped24.4.1213
Upgrade Telerik UI for WPF to version 2024.4.1213 or later. If immediate patching is not possible, disable or restrict deserialization endpoints and implement network-level controls to limit exposure.
24.4.1213 (2024 Q4)
- Upgrade Telerik UI for WPF to version 24.4.1213 (2024 Q4) or later
- Verify the upgrade by checking the Telerik.Wpf.UI assembly version after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10095 — 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-10095 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