dbcve.org
EdgeWeb browser · Microsoft

CVE-2015-2485

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 Internet Explorer 9 through 11 and Microsoft Edge allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Memory Corruption Vulnerability," a different vulnerability than CVE-2015-2491 and CVE-2015-2541.

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

Memory corruption vulnerability in Microsoft Internet Explorer 9 through 11 and Microsoft Edge allows remote attackers to achieve arbitrary code execution or cause denial of service via a specially crafted website. The vulnerability stems from improper memory handling in the browser's rendering engine.

MitigationApply Microsoft security updates (MS15-106) to patch the vulnerability across all affected systems, or use alternative browsers until patches can be deployed.

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
EdgeWeb browser
Affected:all versions
Internet ExplorerApplication
Affected:= 9= 10= 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
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. Check Internet Explorer version
    Open Internet Explorer, click the gear icon (Settings), then 'About Internet Explorer' (or press Alt + H + A). Alternatively, check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Version in the Windows Registry.
    Affected if Version displayed is 9.x, 10.x, or 11.x (the specific versions listed as affected)
  2. Verify Microsoft Edge installation
    Check if Microsoft Edge is present on the system. Look in the Start Menu for Microsoft Edge, or check for the executable at C:\Windows\SystemApps\Microsoft.Windows.Edge_cw5n1h2txyewy\MicrosoftEdge.exe on Windows 10.
    Affected if Microsoft Edge is installed on the system (all versions are affected per the CVE)
  3. Confirm rendering engine version
    Check the mshtml.dll version in the Windows system directory. Open Command Prompt and run: dir %WINDIR%\System32\mshtml.dll (or examine file properties).
    Affected if The DLL version matches the unpatched versions associated with MS15-106 (this requires comparing against Microsoft's security bulletin)

A user is affected if they have Internet Explorer versions 9, 10, or 11, or any version of Microsoft Edge installed and are using the browser to visit untrusted websites.

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-106) to patch the vulnerability across all affected systems, or use alternative browsers until patches can be deployed.

Recommended fix High confidence

Apply Microsoft August 2015 Security Updates (MS15-079)

  1. Open Windows Update by clicking the Start button, then clicking All Programs, and then clicking Windows Update
  2. Check for updates and install all available security updates, particularly the August 2015 security updates for Internet Explorer and Edge
  3. If automatic updates are not enabled, ensure they are turned on to receive future security patches
  4. Restart the computer after installing updates to complete the remediation
  5. Alternatively, apply the Microsoft security update MS15-079 (Cumulative Security Update for Internet Explorer) directly from the Microsoft Update Catalog

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

Fix this in Edge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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