CVE-2024-4202: Progress Telerik Reporting Local Instantiation Vulnerability
First published: Wed May 15 2024(Updated: )
In Progress® Telerik® Reporting versions prior to 2024 Q2 (18.1.24.514), a code execution attack is possible through an insecure instantiation vulnerability.
Credit: security@progress.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Progress Telerik Report Server | <18.1.24.514 |
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-4202?
CVE-2024-4202 is categorized as a critical vulnerability due to the potential for code execution.
How do I fix CVE-2024-4202?
To remediate CVE-2024-4202, upgrade to Progress Telerik Reporting version 2024 Q2 (18.1.24.514) or later.
What versions of Telerik Reporting are affected by CVE-2024-4202?
CVE-2024-4202 affects all versions of Progress Telerik Reporting prior to version 2024 Q2 (18.1.24.514).
What type of attack does CVE-2024-4202 allow?
CVE-2024-4202 allows for a code execution attack due to an insecure instantiation vulnerability.
Is there a workaround for CVE-2024-4202?
There are no official workarounds for CVE-2024-4202; upgrading to a fixed version is strongly recommended.
- agent/references
- agent/title
- agent/weakness
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- collector/epss-latest
- source/FIRST
- agent/epss
- 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