Telerik Reporting: Deserialization of Untrusted Data
CVE-2024-1801 is a high-severity deserialization of untrusted data vulnerability in Telerik Reporting from Progress Software, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 2024 Q1 (18.0.24.130), 2024_q1_(18.0.24.130) as the first without the flaw, so updating Telerik Reporting to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.42% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Telerik Reporting to 2024 Q1 (18.0.24.130) or 2024_q1_(18.0.24.130), whichever matches your release line, or a later version.
- Read the advisory on docs.telerik.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | Telerik Reporting | Q1 2007 up to, but not including, 2024 Q1 (18.0.24.130); q1_2007 up to, but not including, 2024_q1_(18.0.24.130) | 2024 Q1 (18.0.24.130), 2024_q1_(18.0.24.130) |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.7 | High | CNA (progress.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in Telerik Reporting
- 7.3 High severity
- 7.8 High severity
- 7.2 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.