dbcve.org
Telerik Report ServerApplication · Progress

CVE-2024-7292

HIGH · 8.8 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 10.2.24.806 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), a credential stuffing attack is possible through improper restriction of excessive login attempts.

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 confidence

Progress Telerik Report Server versions prior to 2024 Q3 (10.2.24.806) lack proper restrictions on excessive login attempts, enabling credential stuffing attacks where attackers can systematically try large numbers of username/password combinations against the authentication endpoint.

MitigationImplement account lockout policies or rate limiting mechanisms to block or temporarily disable accounts after a configurable number of failed login attempts, and consider implementing CAPTCHA for repeated login failures.

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
Telerik Report ServerApplication
Affected:< 10.2.24.806

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Telerik Report Server installation
    Locate the Telerik Report Server installation directory and find the version information, typically in an About page, assembly metadata, or installation logs
    Affected if The installed version is found to be below 10.2.24.806
  2. Check application version via web interface
    Access the Report Server web interface and navigate to the Help or About section to retrieve the exact version number
    Affected if The reported version is prior to 10.2.24.806 or shows 2024 Q2 or earlier
  3. Verify authentication endpoint exposure
    Determine if the Report Server login page is accessible from external networks or the internet by checking firewall rules or reverse proxy configuration
    Affected if The login endpoint is externally accessible without additional access controls
  4. Review rate limiting configuration
    Inspect the Report Server configuration files or administrative settings to determine if rate limiting or account lockout policies are configured for failed login attempts
    Affected if No rate limiting or account lockout mechanism is enabled or configured

You are affected if Telerik Report Server version is below 10.2.24.806 and the login endpoint is accessible without rate limiting or account lockout controls in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.2.24.806 or later
Fixed in 10.2.24.806
Interim mitigation

Implement account lockout policies or rate limiting mechanisms to block or temporarily disable accounts after a configurable number of failed login attempts, and consider implementing CAPTCHA for repeated login failures.

Recommended fix High confidence

Telerik Report Server 10.2.24.806 (2024 Q3) or later

  1. Identify the current version of Telerik Report Server by accessing the Report Server interface or checking the installation
  2. Download Telerik Report Server version 10.2.24.806 (2024 Q3) or later from the official Telerik website (docs.telerik.com)
  3. Review the upgrade documentation and release notes for any specific migration requirements
  4. Create a complete backup of the existing Report Server database and configuration files
  5. Stop the Telerik Report Server service before beginning the upgrade
  6. Install version 10.2.24.806 or newer following the standard upgrade procedure
  7. After installation, verify the new version is running correctly
  8. Test that authentication is working properly and verify the login attempt restrictions are in effect
Caveat Review release notes for 2024 Q3 for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Telerik Report Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7292 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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