dbcve.org
.net FrameworkApplication · Microsoft

CVE-2015-2480

HIGH · 9.3 CVSS v2.0 Published 2015-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The RyuJIT compiler in Microsoft .NET Framework 4.6 produces incorrect code during an attempt at optimization, which allows remote attackers to execute arbitrary code via a crafted .NET application, aka "RyuJIT Optimization Elevation of Privilege Vulnerability," a different vulnerability than CVE-2015-2479 and CVE-2015-2481.

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 · moderate confidence

The RyuJIT compiler in Microsoft .NET Framework 4.6 contains a flaw in its optimization pass that generates incorrect machine code. When a specially crafted .NET application is compiled by this buggy JIT, the resulting binary contains logic errors that can be exploited to achieve arbitrary code execution with elevated privileges.

MitigationApply Microsoft security updates to patch the RyuJIT compiler bug in .NET Framework 4.6; thoroughly test existing .NET applications after patching to ensure compatibility and correct behavior.

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
.net FrameworkApplication
Affected:= 4.6

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

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 .NET Framework 4.6 is installed
    Check the Windows Registry under HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client or Full for a Version value of 4.6.0.x, or use 'Get-ItemProperty' in PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client' | Select-Object Version
    Affected if The installed version matches 4.6.0.x (any 4.6.x release)
  2. Confirm RyuJIT compiler is enabled
    Check the application configuration file (app.config or web.config) for the <configuration><runtime><enforceFIPSPolicy> element with useLegacyJit enabled, or check registry key HKLM\SOFTWARE\Microsoft\.NETFramework\UseLegacyJit for value 1. If neither exists, RyuJIT is active by default in .NET 4.6.
    Affected if RyuJIT is the active JIT compiler (useLegacyJit is not set to 1) AND .NET 4.6 is installed
  3. Identify applications compiled by RyuJIT
    Review compiled .NET assemblies in application bin directories, particularly those built between the .NET 4.6 release date and the patch date. Check build logs or CI/CD systems for applications compiled during that timeframe.
    Affected if Applications were compiled using the RyuJIT compiler in .NET 4.6 before security updates were applied

A system is affected if .NET Framework 4.6 is installed with RyuJIT enabled as the active JIT compiler, and any .NET applications were compiled using that buggy compiler.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates to patch the RyuJIT compiler bug in .NET Framework 4.6; thoroughly test existing .NET applications after patching to ensure compatibility and correct behavior.

Recommended fix Moderate confidence

Apply Microsoft security update for .NET Framework 4.6 (refer to MS15-080 or subsequent security bulletins for CVE-2015-2480)

  1. Open Windows Update by clicking the Start button and searching for 'Windows Update'
  2. Click 'Check for updates' to see if updates are available
  3. Install any available security updates that include a fix for .NET Framework vulnerabilities (particularly MS15-080 or related security bulletins)
  4. If automatic updates are disabled, manually download and install the relevant security update from the Microsoft Security Bulletin page
  5. Restart the system after installing the update
  6. Verify the update was installed successfully by checking the installed updates in Control Panel > Programs and Features > View installed updates
Caveat Security updates typically have minimal breaking changes, but test critical .NET applications after applying the update to ensure compatibility

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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