dbcve.org
.net FrameworkApplication · Microsoft

CVE-2015-2435

HIGH · 9.3 CVSS v2.0 Published 2015-08-15
Fix available
A fix is available. Upgrade to after 5.1.40416.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 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 Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, Windows 10, Office 2007 SP3 and 2010 SP2, Live Meeting 2007 Console, Lync 2010, Lync 2010 Attendee, Lync 2013 SP1, Lync Basic 2013 SP1, and Silverlight before 5.1.40728 allow remote attackers to execute arbitrary code via a crafted TrueType font, aka "TrueType Font Parsing 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
How this class of weakness works · CWE-20

The application accepts input without confirming it is well-formed or within expected bounds, so malformed data can push the program into states its author never anticipated. Attackers probe these gaps to trigger crashes, bypass logic, or feed tainted values into more dangerous operations downstream. Remediating it well means validating and normalising every input at the boundary against a strict allow-list — not merely filtering known-bad values.

General guidance for the improper input validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
.net FrameworkApplication
Affected:= 3.0= 4.0= 4.5= 4.5.1= 4.5.2= 4.6= 3.5.1= 3.5
Live MeetingApplication
Affected:= 2007
LyncApplication
Affected:= 2010= 2013
Lync BasicApplication
Affected:= 2013
OfficeApplication
Affected:= 2007= 2010
SilverlightApplication
Affected:<= 5.1.40416.0
Windows 10Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 a release after 5.1.40416.0
Vendor patch docs.microsoft.com →
Recommended fix High confidence

Apply MS15-080 security updates; for Silverlight specifically, upgrade to version 5.1.40728 or later

  1. Navigate to Microsoft Security Bulletin MS15-080 at https://docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-080
  2. Identify your affected product from the list: Windows OS version, .NET Framework version, Office version, Lync, Live Meeting, or Silverlight
  3. Download and install the applicable security update(s) listed in the 'Affected Software' section of MS15-080 for your specific product and version
  4. For Silverlight users: Uninstall the current Silverlight version and install Silverlight version 5.1.40728 or later from https://www.microsoft.com/getsilverlight/
  5. Restart the affected system if prompted after patch installation
  6. Verify the update was applied successfully by checking Windows Update history or the program's version information
Caveat This is a security patch with no expected breaking changes; however, ensure backups exist before applying system updates

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2435 — 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-2015-2435 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