CVE-2024-4358
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceProgress Telerik Report Server versions 2024 Q1 (10.0.24.305) and earlier running on IIS contain an authentication bypass vulnerability allowing unauthenticated attackers to access restricted server functionality. The flaw enables complete compromise of the report server without valid credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.0.24.305CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Telerik Report Server installationLocate the Telerik Report Server installation directory or check the installed programs list on the Windows server. The application is typically installed under C:\Program Files\Telerik\Report Server or similar paths depending on the installation.Affected if The installed version is 10.0.24.305 or any earlier version of the 2024 release train.
-
Determine the exact version numberCheck the Report Server version through the application's About page, the bin folder containing the ReportServer.dll file (right-click > Properties > Details), or the Windows installed programs list.Affected if The version displays as 10.0.24.305 or lower (such as 10.0.24.xxx, 10.0.23.xxx, etc.).
-
Verify IIS hosting configurationConfirm that Telerik Report Server is hosted on IIS by checking the IIS Manager for the website/application or reviewing the server's installed roles and features.Affected if The Report Server is configured as an IIS website or application using IIS authentication modules.
-
Check authentication settings in IISReview the IIS authentication configuration for the Report Server site or application in IIS Manager. Look for the enabled authentication methods under the Authentication feature.Affected if The site relies on IIS authentication that can be bypassed, allowing unauthenticated access to restricted endpoints.
You are affected if Telerik Report Server version 10.0.24.305 or earlier is installed and exposed via IIS, as the authentication bypass allows unauthenticated access to protected functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately upgrade Telerik Report Server to a version beyond 2024 Q1 (10.0.24.305) that addresses this authentication bypass. If immediate patching is not feasible, review IIS authentication configuration and implement additional access controls as a temporary measure.
Telerik Report Server 2024 Q2 or later (version > 10.0.24.305)
- 1. Identify the current installed version of Telerik Report Server by checking the About section in the Report Server UI or examining the installation directory
- 2. Back up the Report Server database and configuration files before proceeding with any upgrade
- 3. Download the latest version of Telerik Report Server from the official Progress/Telerik download portal (telerik.com)
- 4. Execute the installer and follow the on-screen prompts to upgrade the Report Server installation
- 5. After upgrade completes, verify that the Report Server service is running correctly
- 6. Confirm the vulnerability is resolved by attempting to access restricted functionality without authentication (this should now fail)
- 7. Review and test critical Report Server workflows to ensure normal operations are intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data