CVE-2024-7292 Vulnerability Analysis & Exploit Details

CVE-2024-7292
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2024-7292 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2024-7292 Details

Status: Analyzed

Last updated: 🕝 15 Oct 2024, 14:50 UTC
Originally published on: 🕒 09 Oct 2024, 15:15 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE-2024-7292 Vulnerability Summary

CVE-2024-7292: 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.

Assessing the Risk of CVE-2024-7292

Access Complexity Graph

The exploitability of CVE-2024-7292 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-7292

With low attack complexity and no required privileges, CVE-2024-7292 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-7292, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-7292, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2024-7292 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-7292 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-7292 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.091% (probability of exploit)

EPSS Percentile: 41.22% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 58.78% of others.

CVE-2024-7292 References

External References

CWE Common Weakness Enumeration

CWE-307

CAPEC Common Attack Pattern Enumeration and Classification

  • Dictionary-based Password Attack CAPEC-16 An attacker tries each of the words in a dictionary as passwords to gain access to the system via some user's account. If the password chosen by the user was a word within the dictionary, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern. Dictionary Attacks differ from similar attacks such as Password Spraying (CAPEC-565) and Credential Stuffing (CAPEC-600), since they leverage unknown username/password combinations and don't care about inducing account lockouts.
  • Password Brute Forcing CAPEC-49 An adversary tries every possible value for a password until they succeed. A brute force attack, if feasible computationally, will always be successful because it will essentially go through all possible passwords given the alphabet used (lower case letters, upper case letters, numbers, symbols, etc.) and the maximum length of the password.
  • Use of Known Domain Credentials CAPEC-560 An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service.
  • Password Spraying CAPEC-565 In a Password Spraying attack, an adversary tries a small list (e.g. 3-5) of common or expected passwords, often matching the target's complexity policy, against a known list of user accounts to gain valid credentials. The adversary tries a particular password for each user account, before moving onto the next password in the list. This approach assists the adversary in remaining undetected by avoiding rapid or frequent account lockouts. The adversary may then reattempt the process with additional passwords, once enough time has passed to prevent inducing a lockout.
  • Credential Stuffing CAPEC-600 An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services.
  • Use of Known Kerberos Credentials CAPEC-652 An adversary obtains (i.e. steals or purchases) legitimate Kerberos credentials (e.g. Kerberos service account userID/password or Kerberos Tickets) with the goal of achieving authenticated access to additional systems, applications, or services within the domain.
  • Use of Known Operating System Credentials CAPEC-653 An adversary guesses or obtains (i.e. steals or purchases) legitimate operating system credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the system, under the guise of an authenticated user or service. This applies to any Operating System.

Vulnerable Configurations

  • cpe:2.3:a:progress:telerik_report_server:-:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:-:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:1.1.15.624:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:1.1.15.624:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:1.2.15.930:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:1.2.15.930:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:1.2.15.1106:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:1.2.15.1106:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:2.0.16.113:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:2.0.16.113:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:2.0.16.204:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:2.0.16.204:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:2.1.16.504:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:2.1.16.504:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:2.1.16.615:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:2.1.16.615:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:2.2.16.914:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:2.2.16.914:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.0.17.301:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.0.17.301:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.0.17.406:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.0.17.406:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.1.17.503:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.1.17.503:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.1.17.614:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.1.17.614:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.2.17.913:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.2.17.913:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:3.2.17.1025:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:3.2.17.1025:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.0.18.117:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.0.18.117:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.0.18.125:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.0.18.125:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.0.18.227:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.0.18.227:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.0.18.417:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.0.18.417:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.1.18.516:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.1.18.516:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.1.18.620:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.1.18.620:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.2.18.912:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.2.18.912:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.2.18.1017:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.2.18.1017:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:4.2.18.1129:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:4.2.18.1129:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.0.19.116:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.0.19.116:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.0.19.222:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.0.19.222:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.1.19.514:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.1.19.514:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.1.19.618:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.1.19.618:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.2.19.918:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.2.19.918:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:5.2.19.1030:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:5.2.19.1030:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.0.20.115:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.0.20.115:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.0.20.219:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.0.20.219:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.1.20.513:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.1.20.513:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.1.20.618:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.1.20.618:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.2.20.916:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.2.20.916:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:6.2.20.1021:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:6.2.20.1021:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.0.21.120:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.0.21.120:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.0.21.224:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.0.21.224:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.0.21.326:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.0.21.326:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.1.21.512:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.1.21.512:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.1.21.616:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.1.21.616:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.2.21.915:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.2.21.915:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.2.21.1110:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.2.21.1110:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:7.2.21.1125:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:7.2.21.1125:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.0.22.119:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.0.22.119:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.0.22.225:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.0.22.225:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.1.22.511:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.1.22.511:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.1.22.622:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.1.22.622:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.2.22.914:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.2.22.914:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:8.2.22.1109:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:8.2.22.1109:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.0.23.118:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.0.23.118:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.0.23.315:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.0.23.315:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.1.23.606:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.1.23.606:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.1.23.718:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.1.23.718:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.2.23.1010:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.2.23.1010:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.2.23.1114:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.2.23.1114:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:9.2.24.305:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:9.2.24.305:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:10.0.24.130:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:10.0.24.130:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:10.0.24.305:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:10.0.24.305:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:10.1.24.514:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:10.1.24.514:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:10.1.24.709:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:10.1.24.709:*:*:*:*:*:*:*
  • cpe:2.3:a:progress:telerik_report_server:10.2.16.1025:*:*:*:*:*:*:*
    cpe:2.3:a:progress:telerik_report_server:10.2.16.1025:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-7292: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...