User-level code execution via unsafe ObjectReader deserialization
Published Mar 20, 2024 · Updated Dec 16, 2025
Insecure deserialization in Telerik Reporting before 2024 Q1 (18.0.24.130) allows remote attackers to execute code through malicious content. The ObjectReader class fails to validate user-supplied data before deserializing it. Exploitation requires the target to visit a malicious page or open a malicious file, and the resulting code runs as the current user.
Summary
What happened
Insecure deserialization in Telerik Reporting before 2024 Q1 (18.0.24.130) allows remote attackers to execute code through malicious content. The ObjectReader class fails to validate user-supplied data before deserializing it. Exploitation requires the target to visit a malicious page or open a malicious file, and the resulting code runs as the current user.
The record
- CVE
- CVE-2024-1801
- Published
- Mar 20, 2024
- Updated
- Dec 16, 2025
- Vendor
- Progress Software Corporation
- Product
- Telerik Reporting
- Classifications
- CWE-502, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=q1_2007 <2024_q1_(18.0.24.130)
- Affected versionversion=Q1 2007 <2024 Q1 (18.0.24.130)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo