Security Resilience

CVE-2017-9248

Exposed Creds in Progress Sitefinity ≤ 10.0.6412.0

CISA KEVActive ExploitationEUVD ExploitedPublic PoCExposed Creds
Published
03 July 2017
Modified
21 April 2026
KEV Added
03 November 2021
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.75 99.5th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2017-9248 is a critical-severity Insufficiently Protected Credentials (CWE-522) vulnerability in Progress Sitefinity. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 0.5% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2017-9248 affects Telerik.Web.UI.dll in Progress Telerik UI for ASP.NET AJAX versions prior to R2 2017 SP1 and Sitefinity versions prior to 10.0.6412.0. The component fails to adequately protect the Telerik.Web.UI.DialogParametersEncryptionKey or the ASP.NET MachineKey, enabling remote attackers to bypass cryptographic protections as classified under CWE-522.

Unauthenticated attackers can exploit the flaw over the network to obtain the MachineKey, facilitating arbitrary file uploads or downloads, cross-site scripting, or compromise of ASP.NET ViewState, resulting in a CVSS 3.1 base score of 9.8.

Telerik security advisories and knowledge-base articles direct administrators to apply the R2 2017 SP1 update for UI for ASP.NET AJAX or version 10.0.6412.0 for Sitefinity to restore proper key protection.

Public exploit code for the issue has been published, confirming the cryptographic weakness can be leveraged in practice.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

leak, arbitrary file uploads or downloads, XSS, or ASP.NET ViewState compromise.

CWE(s)
KEV Date Added
03 November 2021

Related Threats

Threat-Actor AttributionAI

AnonOps
Iranian Advanced Persistent Threat Actors Threaten Election-Related Systems | CISA
Google LLC (civil insider-recruitment defendant)
Threat Actors Exploit Progress Telerik Vulnerabilities in Multiple U.S. Government IIS Servers | CISA
Microsoft Corp. (Salesforce / Slack engineer recruitment claims)
Threat Actors Exploit Progress Telerik Vulnerabilities in Multiple U.S. Government IIS Servers | CISA

CVEs Like This One

CVE-2026-7312Same product: Progress Sitefinity
CVE-2019-18935Same product: Telerik Ui For Asp.Net Ajaxboth on KEV
CVE-2017-11317Same product: Telerik Ui For Asp.Net Ajaxboth on KEV
CVE-2026-7313Same product: Progress Sitefinity
CVE-2020-29583Shared CWE-522both on KEV
CVE-2021-30116Shared CWE-522both on KEV
CVE-2021-22681Shared CWE-522both on KEV
CVE-2024-11625Same product: Progress Sitefinity
CVE-2024-1212Same vendor: Progressboth on KEV
CVE-2024-6670Same vendor: Progressboth on KEV

Affected Assets

progress
sitefinity
≤ 10.0.6412.0
telerik
ui for asp.net ajax
≤ 2017.2.503

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-522

Training instructs users on protecting credentials from disclosure or unauthorized access.

addresses: CWE-522

Training records for security awareness and role-based training verify education on credential protection practices, tangibly reducing risks from mishandling or exposing credentials.

addresses: CWE-522

Protecting authenticator content from unauthorized disclosure and modification while requiring protective controls addresses insufficiently protected credentials.

addresses: CWE-522

Rules of behavior include credential protection and non-sharing requirements, reducing exposure of insufficiently protected credentials.

addresses: CWE-522

Terminating or revoking credentials stops use of insufficiently protected or lingering credentials post-termination.

addresses: CWE-522

Requiring confidentiality/integrity protection for stored credentials directly mitigates insufficiently protected credentials on disk or in configuration stores.

addresses: CWE-522

Credentials or keys delivered out-of-band are not exposed to interception or inadequate protection on the main transport.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.10 only requires awareness, a topic-specific acceptable-use policy stating expected behaviours/monitoring, and procedures referencing other controls (e.g. access restrictions, marking, disposal); it performs none of the verb on CWE-522's insecure credential transmission/storage, which requires technical protections like encryption or secure channels that this governance clause does not supply.

blocks

A.5.17 mandates secure allocation, transmission, storage, hashing/encryption per 8.24, strong non-reusable passwords, immediate change of defaults/compromise, and no cleartext — directly stopping exploitation of insufficiently protected credentials with only a bounded remainder (e.g. non-password authenticators or post-storage exposure vectors outside its scope).

blocks

A.6.2 sets contractual terms, NDAs, and communicates responsibilities to personnel; it has no technical effect on how credentials are protected in transmission or storage and cannot stop exploitation of CWE-522

blocks

Regular reminders about password security and personal accountability make users less likely to store or transmit credentials in cleartext or other unprotected forms.

blocks

A.8.24's purpose, guidance (b,c), and key management mandate proper cryptography (algorithms, strength, protection of credentials in storage/transmission) per classification, which stops exploitation of insufficiently-protected credentials; remainder is bounded (e.g. non-cryptographic protections like hashing-only or non-crypto obfuscation per CWE-522 details).

blocks

A.8.5 mandates MFA, alternative strong methods, no cleartext transmission/storage of passwords, session termination, brute-force protection and secure log-on procedures that directly stop interception/retrieval of credentials even when they exist, leaving only a bounded remainder (e.g. non-password credentials or post-authentication storage outside log-on flows)

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-522, a class-level weakness. Rules are authored against its narrower children: CWE-260, CWE-523.

References