CVE-2024-1801: Progress Telerik Reporting Local Deserialization Vulnerability
First published: Wed Mar 20 2024(Updated: )
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.
Credit: security@progress.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Progress Telerik Report Server | <18.0.24.130 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-1801?
CVE-2024-1801 has a high severity rating due to its potential for code execution by a local threat actor.
How do I fix CVE-2024-1801?
To fix CVE-2024-1801, update Progress® Telerik® Reporting to version 2024 Q1 (18.0.24.130) or later.
Who is affected by CVE-2024-1801?
CVE-2024-1801 affects all versions of Progress® Telerik® Reporting prior to 2024 Q1 (18.0.24.130).
What type of vulnerability is CVE-2024-1801?
CVE-2024-1801 is classified as an insecure deserialization vulnerability.
Can CVE-2024-1801 be exploited remotely?
No, CVE-2024-1801 requires a local threat actor to exploit the vulnerability.
- agent/weakness
- agent/title
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/progress
- canonical/progress telerik report server