CVE-2016-0123
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 · uneditedMicrosoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Microsoft Edge Memory Corruption Vulnerability," a different vulnerability than CVE-2016-0116, CVE-2016-0124, CVE-2016-0129, and CVE-2016-0130.
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 · moderate confidenceMicrosoft Edge contains a memory corruption vulnerability that allows remote attackers to execute arbitrary code or cause a denial of service by tricking users into visiting a specially crafted website. The vulnerability stems from improper memory handling in the Edge rendering engine.
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 dataall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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.
-
Verify Microsoft Edge is installedOpen Start menu and search for Microsoft Edge, or check if the file %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe exists on the systemAffected if Edge is installed and the system has not received the security update for CVE-2016-0123
-
Check the installed Edge versionLaunch Microsoft Edge, click the three-dot menu in the top-right corner, select Settings, then scroll down and click About Microsoft Edge. Alternatively, run 'Get-AppxPackage *MicrosoftEdge* | Select-Object PackageFamilyName, PackageVersion' in PowerShellAffected if The installed version has not been patched to address the memory corruption vulnerability
-
Verify Windows Update patch statusOpen Settings > Update & Security > Windows Update > View update history. Look for a security update installed around the CVE-2016-0123 release date that includes a patch for EdgeAffected if The security update for CVE-2016-0123 is not listed in the installed updates
-
Check if Edge is actively usedReview browser usage logs or interview users to determine if Microsoft Edge is used for browsing websitesAffected if Edge is used to browse websites, since the vulnerability is triggered by visiting specially crafted malicious webpages
If Microsoft Edge is installed, the browser has not been patched via Windows Update, and users browse websites with Edge, the environment is affected by CVE-2016-0123
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 dataApply the Microsoft security update for CVE-2016-0123 via Windows Update to patch the Edge browser. Until patched, avoid browsing untrusted websites and ensure Windows Defender or other endpoint protection is enabled.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0123 — 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-2016-0123 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