dbcve.org
Ui For WpfApplication · Telerik

CVE-2024-8316

HIGH · 7.8 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 2024.3.924 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 Q3 (2024.3.924), 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 Q3 (2024.3.924) contain an insecure deserialization vulnerability that allows remote code execution. Attackers can exploit this by supplying malicious serialized objects to vulnerable deserialization endpoints within the UI framework.

MitigationUpgrade Telerik UI for WPF to version 2024.3.924 or later. If immediate upgrade is not possible, implement network-level controls to limit exposure and monitor for suspicious deserialization activity.

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.3.924

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify Telerik UI for WPF in your application
    Search your project for Telerik.Wpf.dll, Telerik.Windows.Controls.dll, or Telerik UI for WPF NuGet package references in .csproj, packages.config, or the bin/folder
    Affected if Any Telerik WPF assemblies or packages are found in the application
  2. Determine the installed Telerik WPF version
    Right-click each Telerik*.dll in your bin folder, select Properties, then Details to view the File Version. Alternatively, check the version in your NuGet package manager or .csproj package reference
    Affected if The version number is lower than 2024.3.924 (for example, 2024.2.512, 2023.3.1114, etc.)
  3. Check for deserialization endpoints or serialization usage
    Search your codebase for usage of Telerik.Web.UI or Telerik.WinControls serialization-related classes (such as RadXmlHttpPanel, or BinaryFormatter/LosFormatter usage with Telerik controls). Also inspect web.config/app.config for Telerik HTTP handlers
    Affected if The application exposes web-based Telerik endpoints or uses Telerik serialization to process untrusted input
  4. Verify network exposure of Telerik services
    If your WPF application hosts a local web server or service, check which endpoints are bound to network interfaces (not just localhost). Review any HTTP handlers registered for Telerik components in configuration files
    Affected if Telerik deserialization endpoints are accessible from non-localhost network interfaces

You are affected if Telerik UI for WPF version 2024.3.924 or later is not installed AND your application exposes Telerik serialization/deserialization functionality to untrusted input or network attackers.

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.3.924 or later
Fixed in 2024.3.924
Interim mitigation

Upgrade Telerik UI for WPF to version 2024.3.924 or later. If immediate upgrade is not possible, implement network-level controls to limit exposure and monitor for suspicious deserialization activity.

Recommended fix High confidence

2024.3.924 (2024 Q3 release)

  1. 1. Identify the current Telerik UI for WPF NuGet package version in your project (check the .csproj file or packages.config)
  2. 2. Update the Telerik.UI.for.Wpf NuGet package to version 2024.3.924 or later using NuGet Package Manager or by editing the .csproj file
  3. 3. Restore the updated NuGet packages
  4. 4. Rebuild the solution to ensure all dependencies are resolved
  5. 5. Run comprehensive testing of the application to verify functionality after the upgrade
Caveat Review Telerik's release notes for potential breaking changes between your current version and 2024.3.924

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

Fix this in Ui For Wpf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8316 — 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-8316 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