Published: 16/10/2020 Updated: 31/12/2023

CVSS v2 Base Score: 6.8 | Impact Score: 6.4 | Exploitability Score: 8.6

CVSS v3 Base Score: 7.8 | Impact Score: 5.9 | Exploitability Score: 1.8

VMScore: 605

Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

A remote code execution vulnerability exists in the way that Microsoft Windows Codecs Library handles objects in memory. An attacker who successfully exploited the vulnerability could execute arbitrary code. Exploitation of the vulnerability requires that a program process a specially crafted image file. The update addresses the vulnerability by correcting how Microsoft Windows Codecs Library handles objects in memory.

Vulnerable Product	Search on Vulmon	Subscribe to Product
microsoft windows 10 1709
microsoft windows 10 1803
microsoft windows 10 1809
microsoft windows 10 1903
microsoft windows 10 1909
microsoft windows 10 2004

No Sandbox - Applications That Run Chromium and Chrome Without The Sandbox. TL;DR exploits in these browser based applications are already sandboxed escaped: https://no-sandbox.io/

No Sandbox "Applications That Run Chromium Without The Sandbox" Page: no-sandboxio/ Project: githubcom/sickcodes/no-sandbox Twitter: twittercom/sickcodes The Chrome browser uses a sandbox The sandbox status page is found in all Chromium based and Chrome applications: chrome://sandbox See your Chrome sandbox status: chrome://sandbox/ (Righ

First, Patch Tuesday. Now, Oh Hell, Monday: Microsoft emits bonus fixes for Visual Studio, Windows 10 security bugs

The Register • Iain Thomson in San Francisco • 19 Oct 2020

Plus: A warning to SharePoint operators

In brief Just days after issuing fixes for scores of bugs in its products for this month's Patch Tuesday, Microsoft has issued two more patches for security holes that can be exploited by maliciously crafted files to run malware on victims' computers. The first, CVE-2020-17023, is a Visual Studio issue that allows for remote code execution after getting the target to click on a specially crafted package.json file. As for the second, CVE-2020-17022, that's a memory-handling bug in the Windows 10 ...

CVE-2020-17022

Vulnerability Summary

Vulnerability Trend

Github Repositories

Recent Articles

References

Vulmon Search

About

Products

Connect