Threats / Progress / CVE-2017-9248
CVE-2017-9248
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Progress ASP.NET AJAX and Sitefinity vulnerability
Progress Telerik UI for ASP.NET AJAX and Sitefinity contain a cryptographic weakness in Telerik.Web.UI.dll enabling disclosure of encryption keys, XSS attacks, ViewState compromise, and unauthorized file operations.
Verdict
Today item — known-exploited.
A cryptographic implementation flaw in Telerik.Web.UI.dll allows attackers to extract encryption keys and machine credentials, leading to session hijacking, arbitrary code execution via ViewState manipulation, and unauthorized file access on affected ASP.NET applications.
CISA KEV Yes · 2021-11-034EPSS 0.75098 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.75098 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Progress, ASP.NET AJAX and Sitefinity. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-522 Insufficiently Protected Credentials — weakness family: Authentication.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1584 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit the weak cryptographic implementation to extract the DialogParametersEncryptionKey or MachineKey from the application.
Business
Encryption keys are compromised, eliminating cryptographic protections for sensitive application data and session tokens.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Using the disclosed keys, I forge or decrypt the ASP.NET ViewState to inject malicious serialized objects.
Business
Attackers gain remote code execution capability through ViewState deserialization, enabling full application compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I craft XSS payloads through the compromised encryption mechanism to execute arbitrary JavaScript in user browsers.
Business
User sessions are hijacked, credentials are stolen, and malware is distributed to application users.
4
Data at risk — exfiltration narrative 4
Attacker
I leverage the cryptographic weakness to upload malicious files or download sensitive application data.
Business
Confidential business data is exfiltrated and the server is used to host malware or launch further attacks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.