dbcve.org
Ui For WpfApplication · Telerik

CVE-2024-10012

HIGH · 7.8 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 2024.4.1111 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
In Progress Telerik UI for WPF versions prior to 2024 Q4 (2024.4.1111), 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 confidence

Progress Telerik UI for WPF versions prior to 2024.4.1111 contain an insecure deserialization vulnerability that allows remote code execution. An attacker can exploit this by sending specially crafted serialized objects to the affected application, leading to arbitrary code execution on the target system.

MitigationUpgrade Telerik UI for WPF to version 2024.4.1111 (2024 Q4) or later. If immediate patching is not possible, restrict network exposure and implement input validation on 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
Ui For WpfApplication
Affected:< 2024.4.1111

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Telerik UI for WPF version
    Check the version of Telerik.UI.Xaml.dll or Telerik.Windows.Controls.dll in your application bin folder, or review the NuGet package version in your packages.config or .csproj file
    Affected if The version number is less than 2024.4.1111
  2. Determine if RadHtmlChart or Charting is in use
    Search your codebase for references to Telerik.Web.UI or Telerik.Charting namespaces, or check if RadHtmlChart/RadChart controls are used in XAML markup
    Affected if These components utilize the vulnerable deserialization handlers
  3. Check for exposed deserialization endpoints
    Review your application for web service endpoints, WCF services, or HTTP handlers that accept serialized object data, particularly those using BinaryFormatter or Telerik's serialization libraries
    Affected if Such endpoints accept and deserialize untrusted input without validation
  4. Inspect serialization configuration
    Look for app.config or web.config settings related to Telerik serialization, and check for use of Telerik's DataStreamSerializer or similar serialization methods
    Affected if Serialization is configured to allow object deserialization from external sources

You are affected if Telerik UI for WPF version is below 2024.4.1111 AND your application exposes deserialization interfaces that accept serialized objects from potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024.4.1111 or later
Fixed in 2024.4.1111
Interim mitigation

Upgrade Telerik UI for WPF to version 2024.4.1111 (2024 Q4) or later. If immediate patching is not possible, restrict network exposure and implement input validation on deserialization endpoints.

Recommended fix High confidence

2024.4.1111 (2024 Q4 release)

  1. Identify the current Telerik UI for WPF version in your project (check .csproj or packages.config)
  2. Download Telerik UI for WPF version 2024.4.1111 or later from telelerik.com or update via NuGet
  3. Update the Telerik.Ui.Wpf.Core NuGet package reference in your project to version 2024.4.1111 or newer
  4. Restore NuGet packages to ensure the new version is applied
  5. Rebuild the solution to verify the upgrade is successful
  6. Test the application thoroughly to ensure functionality is intact after the upgrade
Caveat Review the Telerik release notes for 2024 Q4 for any potential breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ui For Wpf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10012 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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