dbcve.org
.net FrameworkApplication · Microsoft

CVE-2015-2504

HIGH · 9.3 CVSS v2.0 Published 2015-09-09
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
Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, and 4.6 improperly counts objects before performing an array copy, which allows remote attackers to (1) execute arbitrary code via a crafted XAML browser application (XBAP) or (2) bypass Code Access Security restrictions via a crafted .NET Framework application, aka ".NET Elevation of Privilege 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

Integer overflow vulnerability in Microsoft .NET Framework's array copy operation improperly counts objects before copying, allowing remote code execution via malicious XAML browser applications (XBAP) or bypassing Code Access Security restrictions through crafted .NET applications.

MitigationApply Microsoft security updates (MS15-101) to all affected .NET Framework versions across client and server systems, prioritizing systems running XBAP or hosting untrusted .NET code.

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:= 2.0= 3.5= 3.5.1= 4.0= 4.5= 4.5.1= 4.5.2= 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. Determine installed .NET Framework version
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v*\Release' | Select-Object PSChildName, Version, Release | Format-List. Alternatively, check registry key HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP for subkeys like v2.0, v3.5, v4\Full
    Affected if The installed version matches 2.0, 3.5, 3.5.1, 4.0, 4.5, 4.5.1, 4.5.2, or 4.6 exactly (without later security updates installed)
  2. Verify XBAP support is enabled in Internet Explorer
    In Internet Explorer, go to Internet Options > Security > Custom Level > Enable .NET Framework-based components > XAML browser applications ( XBAP). Check if this setting is enabled or prompt.
    Affected if XBAP is enabled and the system runs Internet Explorer with .NET Framework in the affected version range
  3. Check for Microsoft security updates related to MS15-101
    Open Control Panel > Programs and Features > View installed updates, or run: Get-HotFix | Where-Object {$_.Description -match 'MS15-101'}. Search for updates with KB numbers mentioned in MS15-101 (such as KB3089662, KB3074543, etc.)
    Affected if No MS15-101 updates are installed and the .NET Framework version matches the affected list

The environment is affected if .NET Framework version 2.0, 3.5, 3.5.1, 4.0, 4.5, 4.5.1, 4.5.2, or 4.6 is installed without the corresponding MS15-101 security update, particularly on systems where XBAP is enabled or untrusted .NET code may be executed.

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 (MS15-101) to all affected .NET Framework versions across client and server systems, prioritizing systems running XBAP or hosting untrusted .NET code.

Recommended fix High confidence

Apply Microsoft Security Update MS15-101 (KB3063858/KB3063857) for your specific .NET Framework version

  1. Identify the exact .NET Framework version installed on the affected system using Registry Editor (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\vXX\Version)
  2. For .NET Framework 2.0 SP2 and 4.0: Install security update KB3063858 from Microsoft's security bulletin MS15-101
  3. For .NET Framework 3.5 and 3.5.1: Install security update KB3063857 from MS15-101
  4. For .NET Framework 4.5, 4.5.1, 4.5.2, and 4.6: Install security update KB3063858 from MS15-101
  5. Restart the system after applying the update
  6. Verify the update was successfully installed by checking the installed updates in Programs and Features or via the registry
Caveat Patches are cumulative; ensure compatibility with other installed .NET Framework updates. Test in staging environment before deploying to production.

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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