CVE-2016-0182Critical

Microsoft security update for CVE-2016-0182 — Windows

Published
May 10, 2016
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2016-0182 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2016-0182. This page also shows what EchelonGraph holds for CVE-2016-0182, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products11

  • Windows 10 Version 1511 for 32-bit Systems
  • Windows 10 Version 1511 for x64-based Systems
  • Windows 10 for 32-bit Systems
  • Windows 10 for x64-based Systems
  • Windows 7 for 32-bit Systems Service Pack 1
  • Windows 7 for x64-based Systems Service Pack 1
  • Windows 8.1 for 32-bit systems
  • Windows 8.1 for x64-based systems
  • Windows RT 8.1
  • Windows Vista Service Pack 2
  • Windows Vista x64 Edition Service Pack 2

✅ Updates Microsoft lists: 2 KB articles and 7 other updates

9 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
KB3156387Security Update—
KB3156421Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2016-0182

EchelonGraph score
7.8 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

Windows Journal in Microsoft Windows Vista SP2, Windows 7 SP1, Windows 8.1, Windows RT 8.1, and Windows 10 Gold and 1511 allows remote attackers to execute arbitrary code via a crafted Journal (aka .jnt) file, aka "Windows Journal Memory Corruption Vulnerability."

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2016-0182, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (9)