CVE-2011-0663
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 · uneditedMultiple integer overflows in the Microsoft (1) JScript 5.6 through 5.8 and (2) VBScript 5.6 through 5.8 scripting engines allow remote attackers to execute arbitrary code via a crafted web page, aka "Scripting Memory Reallocation 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 confidenceInteger overflow vulnerabilities exist in the memory reallocation functions of Microsoft JScript 5.6-5.8 and VBScript 5.6-5.8 scripting engines. When processing specially crafted web pages, these overflows allow attackers to corrupt memory and execute arbitrary code remotely.
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.8= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check JScript version on the systemCreate a .js file containing 'WScript.Echo("JScript Version: " + ScriptEngineMajorVersion + "." + ScriptEngineMinorVersion + "." + ScriptEngineBuildVersion);' and execute it with cscript.exe or wscript.exe, or check the jscript.dll file version in %SystemRoot%\System32\jscript.dll using PowerShell: (Get-Item C:\Windows\System32\jscript.dll).VersionInfo.FileVersionAffected if The reported version matches 5.6, 5.7, or 5.8 indicating the installed JScript engine is vulnerable
-
Check VBScript version on the systemCreate a .vbs file containing 'WScript.Echo("VBScript Version: " & ScriptEngineMajorVersion & "." & ScriptEngineMinorVersion & "." & ScriptEngineBuildVersion)' and execute it with cscript.exe or wscript.exe, or check the vbscript.dll file version in %SystemRoot%\System32\vbscript.dll using PowerShell: (Get-Item C:\Windows\System32\vbscript.dll).VersionInfo.FileVersionAffected if The reported version matches 5.6, 5.7, or 5.8 indicating the installed VBScript engine is vulnerable
-
Determine if JScript or VBScript are actively usedCheck for the presence of jscript.dll or vbscript.dll in System32, and review installed software for Internet Explorer or Windows Script Host installations. Query installed Windows features via 'Get-WindowsOptionalFeature -Online' or check for IE/WSH in the systemAffected if Either scripting engine is installed and the versions from steps 1 or 2 match the vulnerable 5.6-5.8 range
If either JScript or VBScript versions 5.6, 5.7, or 5.8 are installed on the system, the environment is affected by this CVE.
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.
From vendor dataDeploy the relevant Microsoft security update (MS11-031) to affected Windows systems, prioritizing internet-facing machines and systems running older Windows versions that include these scripting engines.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0663 — 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-2011-0663 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