CVE-2013-0074
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 · uneditedMicrosoft Silverlight 5, and 5 Developer Runtime, before 5.1.20125.0 does not properly validate pointers during HTML object rendering, which allows remote attackers to execute arbitrary code via a crafted Silverlight application, aka "Silverlight Double Dereference 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 confidenceThis is a double dereference vulnerability in Microsoft Silverlight 5 (and Silverlight 5 Developer Runtime) versions prior to 5.1.20125.0. The vulnerability exists in the HTML object rendering code path where pointers are improperly validated, allowing a crafted Silverlight application to achieve arbitrary code execution on the targeted system.
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>= 5.0, < 5.1.20125.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Silverlight is installedCheck the Windows registry at HKLM\SOFTWARE\Microsoft\Silverlight for a Version key, or look for silverlight.dll in Program FilesAffected if No Silverlight registry key or silverlight.dll file is found on the system
-
Retrieve the installed Silverlight versionRead the Version value from the registry key HKLM\SOFTWARE\Microsoft\Silverlight, or right-click silverlight.dll and view the File Version propertyAffected if The version cannot be determined from registry or file properties
-
Compare version against affected rangeCheck if the installed version is greater than or equal to 5.0 but less than 5.1.20125.0Affected if The installed version is 5.0.x through 5.1.x versions prior to 5.1.20125.0
If Microsoft Silverlight version 5.0 or later but earlier than 5.1.20125.0 is installed, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.1.20125.0
Update Microsoft Silverlight to version 5.1.20125.0 or later to remediate this vulnerability.
Silverlight 5.1.20125.0
- 1. Open the Windows Control Panel and navigate to Programs and Features (or Add or Remove Programs on older Windows versions)
- 2. Locate Microsoft Silverlight in the list of installed programs and note the current version number
- 3. Navigate to the official Microsoft Silverlight download page at https://www.microsoft.com/silverlight/
- 4. Download the latest Silverlight runtime (version 5.1.20125.0 or later)
- 5. Close all web browsers that may be running Silverlight content
- 6. Run the downloaded Silverlight setup installer
- 7. Follow the on-screen prompts to complete the installation
- 8. Restart any web browsers that were closed in step 5
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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