dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022.
Internet ExplorerApplication · Microsoft

CVE-2015-2425

HIGH · 8.8 CVSS v3.1 Published 2015-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges 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 Internet Explorer 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability," a different vulnerability than CVE-2015-2383 and CVE-2015-2384.

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

CVE-2015-2425 is a memory corruption vulnerability in Microsoft Internet Explorer 11 that allows remote attackers to execute arbitrary code or cause a denial of service via a crafted malicious website. The vulnerability stems from improper memory handling in the browser's rendering engine, enabling an attacker to corrupt memory and potentially achieve code execution in the context of the current user.

MitigationApply Microsoft security updates for CVE-2015-2425, or implement compensating controls such as browser isolation, network-level URL filtering, and enhanced endpoint detection rules to identify exploitation attempts until patching is feasible.

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
Internet ExplorerApplication
Affected:= 11

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Internet Explorer 11 is installed
    Open Internet Explorer and navigate to 'About Internet Explorer' (press Alt, click Help, then About Internet Explorer) or check the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer at InstallSource
    Affected if IE version displayed is 11.x.x.x (specifically version 11.0.x) - if version is not 11, this CVE does not apply
  2. Identify the exact build version of Internet Explorer 11
    In the About Internet Explorer dialog, note the full version number (for example, 11.0.9600.17840). Compare this to known affected builds prior to the MS15-065 patch.
    Affected if The build number is lower than the patched version that includes MS15-065 (typically builds prior to the July 2015 security update)
  3. Verify if security update MS15-065 is installed
    Open Control Panel > Programs and Features > View installed updates, or run 'wmic qfe list' command in Command Prompt, and search for KB3078071 (the KB number for MS15-065).
    Affected if KB3078071 is NOT listed in installed updates - the system is likely vulnerable
  4. Check Windows Update history for the security patch
    Open Windows Update history (Control Panel > Windows Update > View update history) and look for 'Security Update for Internet Explorer 11 for Windows [version]' dated July 14, 2015 or later.
    Affected if No security update for IE from July 2015 or later is present in the update history

A user is affected if they have Internet Explorer 11 installed without security update KB3078071 (MS15-065) or subsequent cumulative updates that address this memory corruption flaw.

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
Patch available Apply the vendor patch
Vendor patch docs.microsoft.com →
Interim mitigation

Apply Microsoft security updates for CVE-2015-2425, or implement compensating controls such as browser isolation, network-level URL filtering, and enhanced endpoint detection rules to identify exploitation attempts until patching is feasible.

Recommended fix High confidence

Install the cumulative security update KB3065825 (MS15‑065) which upgrades Internet Explorer 11 to version 11.0.9600.17905 or later.

  1. Open Windows Update or the Microsoft Update Catalog.
  2. Search for the July 2015 cumulative security update for Internet Explorer (KB3065825, also known as MS15‑065).
  3. Download and install the update (or enable Automatic Updates to receive it automatically).
  4. Restart the computer after the update completes.
  5. Verify the installed version of Internet Explorer (Help → About Internet Explorer) is at least 11.0.9600.17905 (the version that includes the CVE‑2015‑2425 fix).
Caveat The patch is a security fix with no expected breaking changes; however, verify compatibility of any legacy ActiveX controls after installation.

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

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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