CVE-2015-2372
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 · uneditedvbscript.dll in Microsoft VBScript 5.6 through 5.8, as used with Internet Explorer 6 through 11 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "VBScript Memory Corruption 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 confidenceThis is a memory corruption vulnerability in the VBScript engine (vbscript.dll) affecting versions 5.6-5.8. Remote attackers can achieve arbitrary code execution or cause denial of service by tricking users into visiting a crafted malicious website that triggers the memory corruption in the VBScript interpreter.
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= 5.6= 5.7= 5.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify VBScript engine versionLocate vbscript.dll on the system (typically in C:\Windows\System32\ or C:\Windows\SysWOW64\), right-click the file, select Properties, then view the Details tab to see the File Version. Alternatively, run `wmic datafile where name="C:\Windows\System32\vbscript.dll" get Version` in Command Prompt.Affected if The version listed is 5.6.x.x, 5.7.x.x, or 5.8.x.x (versions below 5.8.6001.23500 or unpatched builds within the 5.6-5.8 range indicate vulnerability).
-
Verify VBScript execution is enabled in Internet ExplorerOpen Internet Explorer, go to Internet Options > Security > Custom Level, and locate the 'Script ActiveX controls marked safe for scripting' setting. Alternatively, check the registry key at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\ or use Group Policy gpedit.msc under Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Security Features.Affected if VBScript execution is permitted (Enable VBScript is set to Enable or Prompt, not Disabled).
-
Confirm security update KB3072604 (MS15-080) or later is installedOpen Control Panel > Programs and Features > View installed updates, search for KB3072604 or KB3076949 (the specific patches for CVE-2015-2372). Alternatively, run `wmic qfe get HotFixID,InstalledOn | findstr /C:"KB3072604" /C:"KB3076949"` in Command Prompt.Affected if Neither KB3072604 nor KB3076949 (nor any subsequent cumulative update containing the fix) is listed among installed updates.
-
Check for presence of the patched vbscript.dll on diskCompare the actual file version of vbscript.dll against known patched versions (vbscript.dll version 5.8.6001.23500 or higher indicates the patch has been applied). Use `dir vbscript.dll` in System32 to see the version timestamp.Affected if The file version is older than 5.8.6001.23500 or matches an unpatched 5.6-5.8 build.
The system is affected if vbscript.dll version 5.6, 5.7, or 5.8 is present, VBScript execution is enabled in Internet Explorer, and the MS15-080 (KB3072604) or subsequent security update is not installed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Microsoft security updates (MS15-080 and subsequent patches) to address the VBScript vulnerability; alternatively, disable VBScript execution in Internet Explorer via registry settings or Group Policy as a temporary workaround until patching is feasible.
Apply Microsoft security updates KB3068364, KB3068368, or KB3078071 (specific to Windows version) which contain the fix for this vulnerability
- Apply the relevant Microsoft security update for CVE-2015-2372 through Windows Update or the Microsoft Download Center
- For Internet Explorer, ensure all cumulative security updates are installed, particularly MS15-065 (July 2015 Security Update for Internet Explorer)
- Consider disabling VBScript execution in Internet Explorer via Internet Options > Security > Custom Level > Disable Active Scripting for VBScript
- For legacy systems that cannot be patched, restrict access to untrusted websites and enable Enhanced Protected Mode in Internet Explorer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-2372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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