CVE-2024-4358: Progress Telerik Report Server Authentication Bypass by Spoofing Vulnerability
Progress · Telerik Report Server · NVD published 2024-05-29 · posted 2024-06-13 · last modified 2026-06-17
What it is
In Progress Telerik Report Server, version 2024 Q1 (10.0.24.305) or earlier, on IIS, an unauthenticated attacker can gain access to Telerik Report Server restricted functionality via an authentication bypass vulnerability.
| Weakness | CWE-290 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (source: [email protected]) |
| CISA due date | 2024-07-04 (for US federal agencies under BOD; a good deadline for everyone) |
| ATT&CK tactics | Initial Access |
Exploitation evidence
First exploit evidence seen: 2024-06-03 (earliest date across the sources below).
Exploited in the wild
- CISA KEV: listed since 2024-06-13. Source
Public exploit code
Metasploit
auxiliary/scanner/http/telerik_report_server_auth_bypass: Telerik Report Server Auth Bypass (disclosure 2024-06-04)exploit/windows/http/telerik_report_server_deserialization: Telerik Report Server Auth Bypass and Deserialization RCE (disclosure 2024-06-04)
Exploit-DB
- EDB-52103: Progress Telerik Report Server 2024 Q1 (10.0.24.305) - Authentication Bypass (2025-03-28)
GitHub proof-of-concept repositories
6 public repositories from 6 accounts, first seen 2024-06-03. Most starred: sinsinology/CVE-2024-4358 (78 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: CISA KEV · Rapid7 Metasploit Framework module metadata · Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.
Defend the Chain
The attack chain for CVE-2024-4358 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1190 Exploit Public-Facing Application CTID: exploitation technique
CVE-2024-4358 is an authentication bypass vulnerability. This has been seen to be chained with CVE-2024-1800 in order to achieve remote code execution.
How to fix it
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)
Fixed versions
- telerik report server 2024: versions up to and including 10.0.24.305 are affected; check the vendor advisory for the fixed release.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://docs.telerik.com/report-server/knowledge-base/registration-auth-bypass-cve-2024-4358 (CISA KEV notes)
MITRE ATT&CK mitigations for this chain
- M1048 Application Isolation and Sandboxing (for T1190) : Application isolation will limit what other processes and system features the exploited target can access.
- M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
- M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
- M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
- M1026 Privileged Account Management (for T1190) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
- M1050 Exploit Protection (for T1190) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
- M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
- M1051 Update Software (for T1190) : Update software regularly by employing patch management for externally exposed applications.
Detection Generic guidance
- Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.