CVE-2024-1856: Progress Telerik Reporting Remote 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 remote threat actor through an insecure deserialization vulnerability.
Credit: security@progress.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Progress Telerik Reporting | <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-1856?
The severity of CVE-2024-1856 is considered high due to its potential for remote code execution.
How do I fix CVE-2024-1856?
To fix CVE-2024-1856, update Telerik Reporting to version 18.0.24.130 or later.
What software versions are affected by CVE-2024-1856?
CVE-2024-1856 affects all versions of Progress Telerik Reporting prior to 2024 Q1 (18.0.24.130).
Can CVE-2024-1856 be exploited remotely?
Yes, CVE-2024-1856 can be exploited remotely by a threat actor due to an insecure deserialization vulnerability.
What are the potential consequences of CVE-2024-1856 exploitation?
Exploitation of CVE-2024-1856 can lead to unauthorized code execution on the affected system.
- 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 reporting