CriticalCVE-2024-4358

    Registration Authentication Bypass Vulnerability (CVE-2024-4358)

    Published In CISA KEV since Sources: NCSC NZ, pwn.watch, CVE.org

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. Update Progress Software Telerik Report Server to version 10.1.24.514. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Progress Software Telerik Report Server lt 1.0.0..10.1.24.514
    Fixed in
    • Progress Software Telerik Report Server 10.1.24.514

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: NCSC NZ, pwn.watch, CVE.org

    97.5 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.90

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    234.14 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    97.5 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.90
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 14 June 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-290

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is reachable over the network with no authentication and no user interaction, public exploit code exists, and it sits among the CVEs most likely to be exploited. Chained with CVE-2024-1800, it yields full remote code execution on the server. Attackers scan for exposed Report Server instances, which business units often run with direct connections to ERP, CRM, or production databases, making them attractive pivot points. CISA does not currently flag ransomware use, but any internet-reachable instance should still be treated as critical with remediation inside 24 hours. Internal-only deployments warrant high priority in the next maintenance window, within a few days at most.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch: Upgrade Telerik Report Server to 10.1.24.514 (2024 Q2) or later. All versions up to and including 2024 Q1 (10.0.24.305) running on IIS are affected. Patch internet-facing and partner-reachable instances first.
      • Workaround if patching is delayed: Add an IIS URL Rewrite rule that blocks requests to the Startup/Register path (action: AbortRequest or CustomResponse 403). Public exploits abuse this setup endpoint to create a new administrator account.
      • Audit user accounts: List all users in the Report Server admin console. Disable any unknown or recently created accounts, especially those holding the System Administrator role, and open an incident ticket.
      • Cut exposure: Temporarily move internet-facing Report Server instances behind VPN or an IP allowlist until the patch or workaround is verified.
      • If a rogue admin account is found: Assume code execution. Public PoCs chain this bypass with a deserialization flaw (CVE-2024-1800) to achieve RCE as the IIS application pool identity. Isolate the host, take a forensic image, and rotate every credential stored on the server (data source connection strings, service accounts, SMTP).

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Restrict Report Server access to defined client subnets. Do not publish it directly to the internet. Front it with a reverse proxy that enforces pre-authentication (SSO/MFA at the proxy).
      • WAF / reverse proxy: Add a path rule blocking (?i)/Startup/Register for all HTTP methods. Inspect or block report definition uploads (.trdp/.trdx) that contain embedded XAML/ResourceDictionary elements or ObjectDataProvider references to break the RCE chain.
      • Endpoint hardening: Run the IIS app pool under a dedicated, low-privilege identity, never LocalSystem or local admin. Use EDR or AppLocker/WDAC to block cmd.exe, powershell.exe, rundll32.exe, and certutil.exe as children of w3wp.exe.
      • Egress filtering: Allow the Report Server host to reach only its required databases and services. Deny general outbound HTTP(S) to hinder payload staging and reverse shells.
      • IAM / least privilege: Limit the database accounts behind report data sources to read-only, so a compromised server cannot pivot into production data stores with write access.

    3. Runbook step 3

      Detection rules

      • IIS access logs (W3C): Any hit on /Startup/Register after initial setup is suspicious, especially POST requests returning 200 or 302. SPL: index=iis cs_uri_stem="*/Startup/Register*" | stats count by c_ip, cs_method, sc_status, _time
      • Process ancestry (Sysmon EID 1 / Security 4688): w3wp.exe spawning cmd.exe, powershell.exe, whoami.exe, or net.exe on the Report Server host. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "w3wp.exe" and FileName in~ ("cmd.exe","powershell.exe","whoami.exe","net.exe")
      • Application layer: New users created with the admin role, followed shortly by new report uploads from the same account. Diff the Report Server user list against a known-good baseline on a schedule.
      • File system (Sysmon EID 11): New .aspx, .ashx, .dll, or .exe files written by w3wp.exe into the webroot or temp directories indicate webshells or payload drops.
      • Network telemetry (Zeek/Suricata): Outbound connections from the Report Server host to unfamiliar external IPs, especially shortly after a POST to /Startup/Register. Alert on the path with a Suricata rule (http.uri; content:"/Startup/Register"; nocase;).

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NCSC NZ (CC BY 4.0), pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Progress Software CorporationTelerik Report Server
    • 1.0.0 – < 10.1.24.514
    • 10.1.24.514
    telerikreport_server_2024
    • ≤ 10.0.24.305
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-290Authentication Bypass by Spoofing

      Base

      This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

      Entry at MITRE CWE-290

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • docs.telerik.comProgress advisory: CVE-2024-4358Mitigation, Vendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-4358government-resource, US government resource
    • pwn.watchpwn.watch: Progress Telerik Report Server Authentication Bypass by Spoofingpwn-watch
    • NVD (NIST)NVD: CVE-2024-4358pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-4358
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-4358"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-4358.svg?lang=en" alt="CVE-2024-4358 – NEOSEC Intel" height="20"></a>