CVE-2024-6096: Unsafe Deserialization Vulnerability
First published: Wed Jul 24 2024(Updated: )
In Progress® Telerik® Reporting versions prior to 18.1.24.709, a code execution attack is possible through object injection via an insecure type resolution vulnerability.
Credit: security@progress.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Progress Telerik Reporting | <18.1.24.709 |
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-6096?
CVE-2024-6096 is classified as a critical vulnerability due to its potential for code execution attacks.
How do I fix CVE-2024-6096?
To remediate CVE-2024-6096, update Progress Telerik Reporting to version 18.1.24.709 or later.
What versions are affected by CVE-2024-6096?
CVE-2024-6096 affects all versions of Progress Telerik Reporting prior to 18.1.24.709.
What type of attack is associated with CVE-2024-6096?
CVE-2024-6096 is associated with a code execution attack enabled by an insecure type resolution vulnerability.
How can I verify if my software is vulnerable to CVE-2024-6096?
You can verify your software's vulnerability to CVE-2024-6096 by checking if it is running a version earlier than 18.1.24.709.
- agent/title
- agent/weakness
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/severity
- agent/softwarecombine
- collector/the-register
- source/The Register
- alias/CVE-2024-6327
- alias/CVE-2019-18935
- alias/CVE-2024-4358
- alias/CVE-2024-1800
- alias/CVE-2024-6096
- agent/references
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/trending
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/progress
- canonical/progress telerik reporting