dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022. Known ransomware use
SilverlightApplication · Microsoft

CVE-2016-0034

HIGH · 8.8 CVSS v3.1 Published 2016-01-13
Fix available
A fix is available. Upgrade to 5.1.41212.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Silverlight 5 before 5.1.41212.0 mishandles negative offsets during decoding, which allows remote attackers to execute arbitrary code or cause a denial of service (object-header corruption) via a crafted web site, aka "Silverlight Runtime Remote Code Execution Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Microsoft Silverlight 5 before version 5.1.41212.0 contains a flaw in its decoding logic where negative offsets are mishandled, leading to object-header corruption. This memory corruption can be exploited by malicious Silverlight applications or crafted websites to achieve remote code execution or cause a denial of service.

MitigationUpgrade Microsoft Silverlight to version 5.1.41212.0 or later. If Silverlight is no longer required, uninstall it to eliminate the attack surface entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SilverlightApplication
Affected:>= 5.0, < 5.1.41212.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Microsoft Silverlight is installed
    Check for Silverlight installation via Windows Registry at HKLM\SOFTWARE\Microsoft\Silverlight (or look in Programs and Features)
    Affected if Silverlight is found installed on the system
  2. Determine installed Silverlight version
    Read the Version value from the same Silverlight registry key (HKLM\SOFTWARE\Microsoft\Silverlight) or right-click the Microsoft Silverlight entry in Programs and Features to view version
    Affected if The installed version is 5.0 or higher but lower than 5.1.41212.0
  3. Confirm Silverlight browser plugin is enabled
    Open each installed browser (Internet Explorer, Edge, Chrome, Firefox), navigate to Add-ons/Extensions manager, and verify the Silverlight plugin status is set to Enabled
    Affected if The Silverlight browser plugin is enabled in any browser on the system
  4. Assess web browsing context
    Evaluate whether users on this system typically browse untrusted or unknown websites that could serve crafted Silverlight content
    Affected if Users browse to untrusted websites while the vulnerable Silverlight plugin is enabled

A system is affected if Microsoft Silverlight version 5.0 through 5.1.41211.x is installed with the browser plugin enabled and users may visit untrusted websites that could deliver malicious Silverlight content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.1.41212.0 or later
Fixed in 5.1.41212.0
Vendor patch docs.microsoft.com →
Interim mitigation

Upgrade Microsoft Silverlight to version 5.1.41212.0 or later. If Silverlight is no longer required, uninstall it to eliminate the attack surface entirely.

Recommended fix High confidence

5.1.41212.0

  1. Check the current Microsoft Silverlight version installed (typically in Programs and Features or browser add-ons)
  2. Download Silverlight version 5.1.41212.0 or later from the official Microsoft Silverlight download page
  3. Run the installer and complete the installation process
  4. Restart any running web browsers that may have had the old Silverlight plugin loaded
  5. Verify the installed version is 5.1.41212.0 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Silverlight Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0034 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data