Threats / Microsoft / CVE-2013-3896
CVE-2013-3896
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Silverlight vulnerability
Microsoft Silverlight improperly validates pointers during element access, allowing remote attackers to obtain sensitive information through crafted Silverlight applications.
Verdict
Today item — known-exploited.
A remote attacker can craft a malicious Silverlight application that exploits improper pointer validation to read sensitive data from the affected system. This information disclosure vulnerability has been actively exploited in the wild.
CISA KEV Yes · 2022-05-254EPSS 0.6961 (verify live)5CVSS 5.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3Exploit Weaponized · public exploit · Metasploit module10
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 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 2022-05-25).
Probability (EPSS)
EPSS 0.6961 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) · Affected: Microsoft, Silverlight. 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-20 Improper Input Validation.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: no · Technical Impact: partialCISA'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 3150 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.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 craft a malicious Silverlight application that exploits pointer validation flaws to access restricted memory regions.
Business
Sensitive user data, credentials, or system information is exposed to unauthorized parties, creating compliance violations and reputational damage.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the malicious Silverlight application on a compromised or attacker-controlled website and trick users into visiting it.
Business
Widespread data breaches occur as users unknowingly execute the exploit, leading to potential identity theft and financial losses.
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