dbcve.org
Telerik ReportingApplication · Progress

CVE-2024-1801

HIGH · 7.8 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 18.0.24.130 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® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a local threat actor 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 Reporting versions prior to 2024 Q1 (18.0.24.130) contain an insecure deserialization vulnerability that allows a local attacker to achieve arbitrary code execution. The vulnerability stems from the application deserializing untrusted data without proper validation.

MitigationUpgrade Telerik Reporting to version 2024 Q1 (18.0.24.130) or later. Until patched, minimize local access to systems running Telerik Reporting 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
Telerik ReportingApplication
Affected:< 18.0.24.130

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 installed Telerik Reporting version
    Check the Telerik.Reporting.dll assembly version in the installation directory (commonly in C:\Program Files\Telerik\Reporting or the application's bin folder) by right-clicking the DLL, selecting Properties, and viewing the Details tab. Alternatively, check Windows Programs and Features for the installed version.
    Affected if The version shown is lower than 18.0.24.130 (for example, 17.x or earlier releases)
  2. Verify deserialization exposure
    Review application configuration files (such as Web.config or app.config) for endpoints or handlers that accept serialized data. Check for Telerik Report Viewer endpoints, Report Designer connections, or any custom endpoints that process serialized objects.
    Affected if The application exposes endpoints that accept and deserialize data without signature validation (the vulnerability allows arbitrary code execution through untrusted deserialization)
  3. Confirm local access to Telerik Reporting
    Verify that untrusted local users can interact with the Telerik Reporting service, API, or associated file processing. Check file system permissions on report definition files and temporary deserialization directories.
    Affected if Local users with limited privileges can supply malicious serialized payloads to the application (the flaw enables local privilege escalation)
  4. Audit for deserialization gadget usage
    Examine application logs and memory for evidence of deserialization operations. If possible, enable verbose logging for Telerik Reporting and monitor for binary formatter or object deserialization activity.
    Affected if The application deserializes data without validating the type expected versus the type received (insecure deserialization is the root cause)

A system is affected if Telerik Reporting version is below 18.0.24.130 and the application processes deserialized data from untrusted sources or local users.

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 18.0.24.130 or later
Fixed in 18.0.24.130
Interim mitigation

Upgrade Telerik Reporting to version 2024 Q1 (18.0.24.130) or later. Until patched, minimize local access to systems running Telerik Reporting and monitor for suspicious deserialization activity.

Recommended fix High confidence

2024 Q1 (18.0.24.130)

  1. 1. Backup your current project and database before proceeding with the upgrade
  2. 2. Download Telerik Reporting version 18.0.24.130 (2024 Q1) from the official Telerik website or your licensed account
  3. 3. Uninstall the current version of Telerik Reporting from your development environment
  4. 4. Install the new version 18.0.24.130 using the Telerik installer or NuGet package manager
  5. 5. Update all project references to use the new assembly version 18.0.24.130
  6. 6. Rebuild and test your application to ensure compatibility with the new version
  7. 7. Deploy the updated application to your staging environment and verify all reporting functionality works correctly
  8. 8. After successful testing, deploy to production
Caveat Review Telerik's release notes for breaking changes between your current version and 18.0.24.130 before upgrading

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

Fix this in Telerik Reporting Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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