Progress Software Corporation Telerik Report Server vulnerabilities

7 vulnerabilities

Known vulnerabilities in Progress Software Corporation Telerik Report Server, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

9.9CVE-2024-1800progress software corporationtelerik report server+1
EPSS score
34.25%
In Progress® Telerik® Report Server versions prior to 2024 Q1 (10.0.24.130), a remote code execution attack is possible through an insecure deserialization vulnerability.9.8CVE-2024-4358progress software corporationtelerik report server+1KEV
EPSS score
97.48%
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.8.8CVE-2024-7293progress software corporationtelerik report server+1
EPSS score
0.33%
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), a password brute forcing attack is possible through weak password requirements.8.8CVE-2024-7292progress software corporationtelerik report server+1
EPSS score
0.33%
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.7.5CVE-2024-7294progress software corporationtelerik report server+1
EPSS score
0.34%
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), an HTTP DoS attack is possible on anonymous endpoints without rate limiting.7.1CVE-2024-7295progress software corporationtelerik report server+1
EPSS score
0.11%
In Progress® Telerik® Report Server versions prior to 2024 Q4 (10.3.24.1112), the encryption of local asset data used an older algorithm which may allow a sophisticated actor to decrypt this information.9.9CVE-2024-6327progress software corporationtelerik report server+1
EPSS score
2.00%
In Progress® Telerik® Report Server versions prior to 2024 Q2 (10.1.24.709), a remote code execution attack is possible through an insecure deserialization vulnerability.