dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-3134

HIGH · 9.3 CVSS v2.0 Published 2013-07-10
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 Common Language Runtime (CLR) in Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 on 64-bit platforms does not properly allocate arrays of structures, which allows remote attackers to execute arbitrary code via a crafted .NET Framework application that changes array data, aka "Array Allocation 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

The vulnerability exists in the Common Language Runtime (CLR) of Microsoft .NET Framework versions 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 on 64-bit platforms. The CLR incorrectly allocates arrays of structures, leading to memory corruption that can be exploited by a remote attacker through a crafted .NET application to achieve arbitrary code execution.

MitigationApply the Microsoft security update (MS13-052) to all affected .NET Framework installations on 64-bit platforms. Prioritize systems running 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

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 64-bit platform
    Check system architecture by running 'systeminfo' or looking at System Properties > About. The OS must be a 64-bit version (x64) for this vulnerability to apply.
    Affected if The system is running a 32-bit (x86) Windows version - the flaw does not apply.
  2. Identify installed .NET Framework version
    Check the Windows registry key HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Full for the Version value, or use 'reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version' at the command prompt.
    Affected if The installed version is 2.0 SP2, 3.5, 3.5.1, 4.0, or 4.5 on a 64-bit system.
  3. Confirm CLR component presence
    Verify the Common Language Runtime is installed by checking for the presence of mscorlib.dll in the Windows\Microsoft.NET\Framework64\ directory (64-bit CLR).
    Affected if The CLR runtime files exist on the 64-bit system.
  4. Check for untrusted code execution scenarios
    Review systems that run untrusted or user-supplied .NET code, such as web applications hosting untrusted assemblies, .NET remoting endpoints, or systems executing code from untrusted sources.
    Affected if The system runs untrusted .NET code on a 64-bit platform with an affected .NET version.

A system is affected if it runs Microsoft .NET Framework versions 2.0 SP2, 3.5, 3.5.1, 4.0, or 4.5 on a 64-bit (x64) Windows platform.

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 the Microsoft security update (MS13-052) to all affected .NET Framework installations on 64-bit platforms. Prioritize systems running untrusted .NET code.

Recommended fix High confidence

Microsoft .NET Framework 4.8

  1. 1. Identify all systems running affected .NET Framework versions (2.0 SP2, 3.5, 3.5.1, 4, 4.5) on 64-bit platforms.
  2. 2. Review application compatibility for each affected system, as .NET Framework upgrades may require testing.
  3. 3. Download and install .NET Framework 4.8 (the final version of .NET Framework 4.x) from the official Microsoft Download Center or through Windows Update.
  4. 4. Alternatively, if Windows Update is enabled, run Windows Update to receive the appropriate security patches for your specific .NET Framework version.
  5. 5. After installation, restart the affected systems as prompted.
  6. 6. Verify the .NET Framework version installed matches the expected version (4.8 or patched 4.5.x with MS13-052 updates).
  7. 7. Test critical .NET applications to ensure functionality is maintained after the update.
Caveat Upgrading .NET Framework 4.x may require application regression testing; some legacy applications targeting older frameworks may have compatibility issues

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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