# CVE-2017-9248: Progress Telerik UI for ASP.NET AJAX and Sitefinity Cryptographic Weakness

> Weak cryptographic protection in Telerik UI allows attackers to leak keys, enabling file access, XSS, and ViewState compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-mfqq-q5rf-3hvq

## What is CVE-2017-9248?

CVE-2017-9248 is a critical vulnerability in n/a, published on 3 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Telerik.Web.UI.dll in Progress Telerik UI for ASP.NET AJAX before R2 2017 SP1 and Sitefinity before 10.0.6412.0 does not properly protect Telerik.Web.UI.DialogParametersEncryptionKey or the MachineKey, which makes it easier for remote attackers to defeat cryptographic protection mechanisms, leading to a MachineKey leak, arbitrary file uploads or downloads, XSS, or ASP.NET ViewState compromise.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2017-9248?

It affects 2 products.


Products: Progress Sitefinity, Telerik Ui for Asp.net Ajax.

## How do I fix CVE-2017-9248?

No fix has been published for CVE-2017-9248 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-9248 being exploited?

Yes. Attackers have exploited CVE-2017-9248 in the wild since at least 3 Nov 2021.

Public exploit code:

- Base64-based encryption oracle exploit for CVE-2017-9248 (Telerik UI for ASP.NET AJAX dialog handler) (github_poc): https://github.com/bao7uo/dp_crypto
- A Burp extension to detect and exploit versions of Telerik Web UI vulnerable to CVE-2017-9248. (github_poc): https://github.com/capt-meelo/Telewreck
- Another tool for exploiting CVE-2017-9248, a cryptographic weakness in Telerik UI for ASP.NET AJAX dialog handler. (github_poc): https://github.com/blacklanternsecurity/dp_cryptomg
- Telerik CVE-2017-9248 Vulnerability Scanner (github_poc): https://github.com/0xsharz/telerik-scanner-cve-2017-9248
- Telerik UI for ASP.NET AJAX 2012.3.1308 < 2017.1.118 - Encryption Keys Disclosure (exploitdb)
- https://github.com/ictnamanh/CVE-2017-9248 (github_poc): https://github.com/ictnamanh/CVE-2017-9248

## Other vulnerabilities in n/a

- [CVE-2026-7312](https://insights.sbomify.com/CVE-2026-7312/): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity (critical 10.0)
- [CVE-2026-7198](https://insights.sbomify.com/CVE-2026-7198/): CWE-284: Improper Access Control in web services in Progress Sitefinity (critical 9.8)
- [CVE-2023-29375](https://insights.sbomify.com/CVE-2023-29375/): File upload in n/a (critical 9.8)
- [CVE-2019-17392](https://insights.sbomify.com/CVE-2019-17392/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-15883](https://insights.sbomify.com/CVE-2017-15883/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9248 and fix it if it is affected.

What it is: CVE-2017-9248 is a critical vulnerability in n/a, published on 3 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-9248 in the wild since at least 3 Nov 2021.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9248/ (Markdown: https://insights.sbomify.com/CVE-2017-9248/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9248
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9248
- OSV: https://osv.dev/vulnerability/CVE-2017-9248

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9248/
Summaries are generated and may contain mistakes; the official description above is the record.