Progress Telerik Reporting up to 18.2.24.806 externally-controlled input to select classes or code
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Progress Telerik Reporting up to 18.2.24.806. Affected by this issue is some unknown functionality. Performing a manipulation results in use of externally-controlled input to select classes or code. This vulnerability is known as CVE-2024-8048. Attacking locally is a requirement. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Progress Telerik Reporting up to 18.2.24.806. This affects an unknown code. The manipulation with an unknown input leads to a use of externally-controlled input to select classes or code vulnerability. CWE is classifying the issue as CWE-470. The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible using object injection via insecure expression evaluation.
The weakness was published by Markus Wulftange. The advisory is shared at docs.telerik.com. This vulnerability is uniquely identified as CVE-2024-8048 since 08/21/2024. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 208748 (Progress Telerik Reporting <= 2024 Q3 (18.2.24.806) Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 18.2.24.924 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (208748). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (ProgressSoftware): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of externally-controlled input to select classes or codeCWE: CWE-470
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 208748
Nessus Name: Progress Telerik Reporting <= 2024 Q3 (18.2.24.806) Multiple Vulnerabilities
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Telerik Reporting 18.2.24.924
Timeline
08/21/2024 🔍10/09/2024 🔍
10/09/2024 🔍
03/07/2025 🔍
Sources
Advisory: docs.telerik.comResearcher: Markus Wulftange
Status: Confirmed
CVE: CVE-2024-8048 (🔍)
GCVE (CVE): GCVE-0-2024-8048
GCVE (VulDB): GCVE-100-279885
Entry
Created: 10/09/2024 17:17Updated: 03/07/2025 13:40
Changes: 10/09/2024 17:17 (64), 10/11/2024 23:24 (2), 03/07/2025 13:40 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.