Windows iSCSI Target Service Elevation of Privilege Vulnerability
2020-10-13T07:00:00
ID MS:CVE-2020-16980 Type mscve Reporter Microsoft Modified 2020-10-13T07:00:00
Description
An elevation of privilege vulnerability exists when the Windows iSCSI Target Service improperly handles file operations. An attacker who successfully exploited this vulnerability could gain elevated privileges.
To exploit the vulnerability, an attacker would first need code execution on a victim system. An attacker could then run a specially crafted application.
The security update addresses the vulnerability by ensuring the Windows iSCSI Target Service properly handles file operations.
{"id": "MS:CVE-2020-16980", "bulletinFamily": "microsoft", "title": "Windows iSCSI Target Service Elevation of Privilege Vulnerability", "description": "An elevation of privilege vulnerability exists when the Windows iSCSI Target Service improperly handles file operations. An attacker who successfully exploited this vulnerability could gain elevated privileges.\n\nTo exploit the vulnerability, an attacker would first need code execution on a victim system. An attacker could then run a specially crafted application.\n\nThe security update addresses the vulnerability by ensuring the Windows iSCSI Target Service properly handles file operations.\n", "published": "2020-10-13T07:00:00", "modified": "2020-10-13T07:00:00", "cvss": {"score": 4.6, "vector": "AV:L/AC:L/Au:N/C:P/I:P/A:P"}, "href": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16980", "reporter": "Microsoft", "references": [], "cvelist": ["CVE-2020-16980"], "type": "mscve", "lastseen": "2020-10-21T13:31:29", "edition": 2, "viewCount": 0, "enchantments": {"dependencies": {"references": [{"type": "cve", "idList": ["CVE-2020-16980"]}, {"type": "nessus", "idList": ["SMB_NT_MS20_OCT_4577668.NASL", "SMB_NT_MS20_OCT_4580382.NASL", "SMB_NT_MS20_OCT_4580346.NASL", "SMB_NT_MS20_OCT_4580347.NASL"]}, {"type": "kaspersky", "idList": ["KLA11977"]}], "modified": "2020-10-21T13:31:29", "rev": 2}, "score": {"value": 6.0, "vector": "NONE", "modified": "2020-10-21T13:31:29", "rev": 2}, "vulnersScore": 6.0}, "kbList": ["KB4577066", "KB4577671", "KB4570333", "KB4577038", "KB4571756", "KB4580347", "KB4580346", "KB4579311", "KB4580382", "KB4577668", "KB4577015", "KB4574727"], "msrc": "", "mscve": "CVE-2020-16980", "msAffectedSoftware": [{"kb": "KB4577668", "kbSupersedence": "KB4570333", "msplatform": "", "name": "Windows Server 2019"}, {"kb": "KB4579311", "kbSupersedence": "KB4571756", "msplatform": "", "name": "Windows Server, version 2004 (Server Core installation)"}, {"kb": "KB4577671", "kbSupersedence": "KB4574727", "msplatform": "", "name": "Windows Server, version 1903 (Server Core installation)"}, {"kb": "KB4580346", "kbSupersedence": "KB4577015", "msplatform": "", "name": "Windows Server 2016 (Server Core installation)"}, {"kb": "KB4580347", "kbSupersedence": "KB4577066", "msplatform": "", "name": "Windows Server 2012 R2"}, {"kb": "KB4580347", "kbSupersedence": "KB4577066", "msplatform": "", "name": "Windows Server 2012 R2 (Server Core installation)"}, {"kb": "KB4577671", "kbSupersedence": "KB4574727", "msplatform": "", "name": "Windows Server, version 1909 (Server Core installation)"}, {"kb": "KB4580382", "kbSupersedence": "KB4577038", "msplatform": "", "name": "Windows Server 2012"}, {"kb": "KB4580382", "kbSupersedence": "KB4577038", "msplatform": "", "name": "Windows Server 2012 (Server Core installation)"}, {"kb": "KB4580346", "kbSupersedence": "KB4577015", "msplatform": "", "name": "Windows Server 2016"}, {"kb": "KB4577668", "kbSupersedence": "KB4570333", "msplatform": "", "name": "Windows Server 2019 (Server Core installation)"}], "scheme": null}
{"cve": [{"lastseen": "2021-02-02T07:37:01", "description": "An elevation of privilege vulnerability exists when the Windows iSCSI Target Service improperly handles file operations, aka 'Windows iSCSI Target Service Elevation of Privilege Vulnerability'.", "edition": 3, "cvss3": {"exploitabilityScore": 1.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "baseScore": 7.8, "privilegesRequired": "LOW", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "userInteraction": "NONE", "version": "3.1"}, "impactScore": 5.9}, "published": "2020-10-16T23:15:00", "title": "CVE-2020-16980", "type": "cve", "cwe": ["CWE-269"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 4.6, "vectorString": "AV:L/AC:L/Au:N/C:P/I:P/A:P", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "acInsufInfo": false, "impactScore": 6.4, "obtainUserPrivilege": false}, "cvelist": ["CVE-2020-16980"], "modified": "2020-10-20T19:21:00", "cpe": ["cpe:/o:microsoft:windows_server_2019:-", "cpe:/o:microsoft:windows_server_2016:2004", "cpe:/o:microsoft:windows_server_2012:r2", "cpe:/o:microsoft:windows_server_2016:1909", "cpe:/o:microsoft:windows_server_2012:-", "cpe:/o:microsoft:windows_server_2016:-", "cpe:/o:microsoft:windows_server_2016:1903"], "id": "CVE-2020-16980", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16980", "cvss": {"score": 4.6, "vector": "AV:L/AC:L/Au:N/C:P/I:P/A:P"}, "cpe23": ["cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:1903:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:-:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:2004:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:1909:*:*:*:*:*:*:*"]}], "nessus": [{"lastseen": "2020-11-15T06:24:37", "description": "The remote Windows host is missing security update 4580353\nor cumulative update 4580382. It is, therefore, affected by\nmultiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16920)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-16923)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)", "edition": 6, "cvss3": {"score": 7.8, "vector": "AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2020-10-13T00:00:00", "title": "KB4580353: Windows Server 2012 October 2020 Security Update", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2020-16911", "CVE-2020-16889", "CVE-2020-16939", "CVE-2020-16937", "CVE-2020-16891", "CVE-2020-16902", "CVE-2020-16892", "CVE-2020-16900", "CVE-2020-16897", "CVE-2020-16935", "CVE-2020-16923", "CVE-2020-16887", "CVE-2020-16916", "CVE-2020-16924", "CVE-2020-16980", "CVE-2020-16922", "CVE-2020-16940", "CVE-2020-16920", "CVE-2020-16914"], "modified": "2020-10-13T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS20_OCT_4580382.NASL", "href": "https://www.tenable.com/plugins/nessus/141426", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from the Microsoft Security Updates API. The text\n# itself is copyright (C) Microsoft Corporation.\n#\n\ninclude('compat.inc');\n\nif (description)\n{\n script_id(141426);\n script_version(\"1.6\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2020/11/13\");\n\n script_cve_id(\n \"CVE-2020-16887\",\n \"CVE-2020-16889\",\n \"CVE-2020-16891\",\n \"CVE-2020-16892\",\n \"CVE-2020-16897\",\n \"CVE-2020-16900\",\n \"CVE-2020-16902\",\n \"CVE-2020-16911\",\n \"CVE-2020-16914\",\n \"CVE-2020-16916\",\n \"CVE-2020-16920\",\n \"CVE-2020-16922\",\n \"CVE-2020-16923\",\n \"CVE-2020-16924\",\n \"CVE-2020-16935\",\n \"CVE-2020-16937\",\n \"CVE-2020-16939\",\n \"CVE-2020-16940\",\n \"CVE-2020-16980\"\n );\n script_xref(name:\"MSKB\", value:\"4580353\");\n script_xref(name:\"MSKB\", value:\"4580382\");\n script_xref(name:\"MSFT\", value:\"MS20-4580353\");\n script_xref(name:\"MSFT\", value:\"MS20-4580382\");\n script_xref(name:\"IAVA\", value:\"2020-A-0458-S\");\n\n script_name(english:\"KB4580353: Windows Server 2012 October 2020 Security Update\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote Windows host is affected by multiple vulnerabilities.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote Windows host is missing security update 4580353\nor cumulative update 4580382. It is, therefore, affected by\nmultiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16920)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-16923)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4580353\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4580382\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Security Only update KB4580353 or Cumulative Update KB4580382.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:U/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:U/RL:O/RC:C\");\n script_set_attribute(attribute:\"cvss_score_source\", value:\"CVE-2020-16924\");\n\n script_set_attribute(attribute:\"exploitability_ease\", value:\"No known exploits are available\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2020/10/13\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_copyright(english:\"This script is Copyright (C) 2020 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n\n script_dependencies(\"smb_check_rollup.nasl\", \"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, \"Host/patch_management_checks\");\n\n exit(0);\n}\n\ninclude('smb_func.inc');\ninclude('smb_hotfixes.inc');\ninclude('smb_hotfixes_fcheck.inc');\ninclude('smb_reg_query.inc');\ninclude('install_func.inc');\n\nget_kb_item_or_exit('SMB/MS_Bulletin_Checks/Possible');\n\nbulletin = 'MS20-10';\nkbs = make_list(\n '4580382',\n '4580353'\n);\n\nif (get_kb_item('Host/patch_management_checks')) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit('SMB/Registry/Enumerated');\nget_kb_item_or_exit('SMB/WindowsVersion', exit_code:1);\n\nif (hotfix_check_sp_range(win8:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\n# Windows 8 EOL\nproductname = get_kb_item_or_exit(\"SMB/ProductName\", exit_code:1);\nif (\"Windows 8\" >< productname) audit(AUDIT_OS_SP_NOT_VULN);\n\nshare = hotfix_get_systemdrive(as_share:TRUE, exit_on_fail:TRUE);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n smb_check_rollup(os:'6.2', \n sp:0,\n rollup_date:'10_2020',\n bulletin:bulletin,\n rollup_kb_list:[4580382, 4580353])\n)\n{\n replace_kb_item(name:'SMB/Missing/'+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, hotfix_get_audit_report());\n}\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-11-15T06:24:37", "description": "The remote Windows host is missing security update 4580358\nor cumulative update 4580347. It is, therefore, affected by\nmultiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16920)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-16923)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)", "edition": 6, "cvss3": {"score": 7.8, "vector": "AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2020-10-13T00:00:00", "title": "KB4580358: Windows 8.1 and Windows Server 2012 R2 October 2020 Security Update", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2020-16911", "CVE-2020-16889", "CVE-2020-16939", "CVE-2020-16937", "CVE-2020-16891", "CVE-2020-16902", "CVE-2020-16892", "CVE-2020-16900", "CVE-2020-16927", "CVE-2020-16896", "CVE-2020-16897", "CVE-2020-16935", "CVE-2020-16923", "CVE-2020-16887", "CVE-2020-16916", "CVE-2020-16924", "CVE-2020-16980", "CVE-2020-16922", "CVE-2020-16940", "CVE-2020-16920", "CVE-2020-16914"], "modified": "2020-10-13T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS20_OCT_4580347.NASL", "href": "https://www.tenable.com/plugins/nessus/141416", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from the Microsoft Security Updates API. The text\n# itself is copyright (C) Microsoft Corporation.\n#\n\ninclude('compat.inc');\n\nif (description)\n{\n script_id(141416);\n script_version(\"1.6\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2020/11/13\");\n\n script_cve_id(\n \"CVE-2020-16887\",\n \"CVE-2020-16889\",\n \"CVE-2020-16891\",\n \"CVE-2020-16892\",\n \"CVE-2020-16896\",\n \"CVE-2020-16897\",\n \"CVE-2020-16900\",\n \"CVE-2020-16902\",\n \"CVE-2020-16911\",\n \"CVE-2020-16914\",\n \"CVE-2020-16916\",\n \"CVE-2020-16920\",\n \"CVE-2020-16922\",\n \"CVE-2020-16923\",\n \"CVE-2020-16924\",\n \"CVE-2020-16927\",\n \"CVE-2020-16935\",\n \"CVE-2020-16937\",\n \"CVE-2020-16939\",\n \"CVE-2020-16940\",\n \"CVE-2020-16980\"\n );\n script_xref(name:\"MSKB\", value:\"4580358\");\n script_xref(name:\"MSKB\", value:\"4580347\");\n script_xref(name:\"MSFT\", value:\"MS20-4580358\");\n script_xref(name:\"MSFT\", value:\"MS20-4580347\");\n script_xref(name:\"IAVA\", value:\"2020-A-0458-S\");\n\n script_name(english:\"KB4580358: Windows 8.1 and Windows Server 2012 R2 October 2020 Security Update\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote Windows host is affected by multiple vulnerabilities.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote Windows host is missing security update 4580358\nor cumulative update 4580347. It is, therefore, affected by\nmultiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16920)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-16923)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4580358/windows-8-1-update\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4580347/windows-8-1-update\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Security Only update KB4580358 or Cumulative Update KB4580347.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:U/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:U/RL:O/RC:C\");\n script_set_attribute(attribute:\"cvss_score_source\", value:\"CVE-2020-16924\");\n\n script_set_attribute(attribute:\"exploitability_ease\", value:\"No known exploits are available\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2020/10/13\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_copyright(english:\"This script is Copyright (C) 2020 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n\n script_dependencies(\"smb_check_rollup.nasl\", \"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, \"Host/patch_management_checks\");\n\n exit(0);\n}\n\ninclude('smb_func.inc');\ninclude('smb_hotfixes.inc');\ninclude('smb_hotfixes_fcheck.inc');\ninclude('smb_reg_query.inc');\ninclude('install_func.inc');\n\nget_kb_item_or_exit('SMB/MS_Bulletin_Checks/Possible');\n\nbulletin = 'MS20-10';\nkbs = make_list(\n '4580347',\n '4580358'\n);\n\nif (get_kb_item('Host/patch_management_checks')) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit('SMB/Registry/Enumerated');\nget_kb_item_or_exit('SMB/WindowsVersion', exit_code:1);\n\nif (hotfix_check_sp_range(win81:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\n# Windows 8 EOL\nproductname = get_kb_item_or_exit(\"SMB/ProductName\", exit_code:1);\nif (\"Windows 8\" >< productname && \"8.1\" >!< productname)\n audit(AUDIT_OS_SP_NOT_VULN);\n\nshare = hotfix_get_systemdrive(as_share:TRUE, exit_on_fail:TRUE);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n smb_check_rollup(os:'6.3', \n sp:0,\n rollup_date:'10_2020',\n bulletin:bulletin,\n rollup_kb_list:[4580347, 4580358])\n)\n{\n replace_kb_item(name:'SMB/Missing/'+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, hotfix_get_audit_report());\n}\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-11-15T06:24:36", "description": "The remote Windows host is missing security update 4580346.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - A remote code execution vulnerability exists when\n Windows Network Address Translation (NAT) fails to\n properly handle UDP traffic. (CVE-2020-16894)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage VSP Driver improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16885)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-1167, CVE-2020-16923)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage Services improperly handle file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-0764)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16876, CVE-2020-16920)\n\n - A memory corruption vulnerability exists when Windows\n Media Foundation improperly handles objects in memory.\n An attacker who successfully exploited the vulnerability\n could install programs; view, change, or delete data; or\n create new accounts with full user rights. There are\n multiple ways an attacker could exploit the\n vulnerability, such as by convincing a user to open a\n specially crafted document, or by convincing a user to\n visit a malicious webpage. The security update addresses\n the vulnerability by correcting how Windows Media\n Foundation handles objects in memory. (CVE-2020-16915)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - A security feature bypass vulnerability exists when\n Microsoft Windows fails to handle file creation\n permissions, which could allow an attacker to create\n files in a protected Unified Extensible Firmware\n Interface (UEFI) location. (CVE-2020-16910)\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists in\n Windows Error Reporting (WER) when WER handles and\n executes files. The vulnerability could allow elevation\n of privilege if an attacker can successfully exploit it.\n An attacker who successfully exploited the vulnerability\n could gain greater access to sensitive information and\n system functionality. (CVE-2020-16905, CVE-2020-16909)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n specific malicious data from a user on a guest operating\n system. (CVE-2020-1243)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows Backup Service improperly handles file\n operations. (CVE-2020-16912, CVE-2020-16936,\n CVE-2020-16972, CVE-2020-16973, CVE-2020-16974,\n CVE-2020-16975, CVE-2020-16976)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - An information disclosure vulnerability exists when the\n Windows Enterprise App Management Service improperly\n handles certain file operations. An attacker who\n successfully exploited this vulnerability could read\n arbitrary files. An attacker with unprivileged access to\n a vulnerable system could exploit this vulnerability.\n The security update addresses the vulnerability by\n ensuring the Windows Enterprise App Management Service\n properly handles file operations. (CVE-2020-16919)", "edition": 6, "cvss3": {"score": 7.8, "vector": "AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2020-10-13T00:00:00", "title": "KB4580346: Windows 10 Version 1607 and Windows Server 2016 October 2020 Security Update", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2020-16975", "CVE-2020-16905", "CVE-2020-16911", "CVE-2020-16889", "CVE-2020-16939", "CVE-2020-16972", "CVE-2020-16937", "CVE-2020-16974", "CVE-2020-16885", "CVE-2020-16891", "CVE-2020-16902", "CVE-2020-16936", "CVE-2020-16892", "CVE-2020-16900", "CVE-2020-16927", "CVE-2020-16910", "CVE-2020-16896", "CVE-2020-16909", "CVE-2020-16915", "CVE-2020-16897", "CVE-2020-16976", "CVE-2020-16935", "CVE-2020-16923", "CVE-2020-16887", "CVE-2020-16916", "CVE-2020-16894", "CVE-2020-16924", "CVE-2020-16980", "CVE-2020-16922", "CVE-2020-16940", "CVE-2020-1167", "CVE-2020-16920", "CVE-2020-16912", "CVE-2020-16876", "CVE-2020-0764", "CVE-2020-1243", "CVE-2020-16914", "CVE-2020-16919", "CVE-2020-16973"], "modified": "2020-10-13T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS20_OCT_4580346.NASL", "href": "https://www.tenable.com/plugins/nessus/141434", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from the Microsoft Security Updates API. The text\n# itself is copyright (C) Microsoft Corporation.\n#\n\ninclude('compat.inc');\n\nif (description)\n{\n script_id(141434);\n script_version(\"1.6\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2020/11/13\");\n\n script_cve_id(\n \"CVE-2020-0764\",\n \"CVE-2020-1167\",\n \"CVE-2020-1243\",\n \"CVE-2020-16876\",\n \"CVE-2020-16885\",\n \"CVE-2020-16887\",\n \"CVE-2020-16889\",\n \"CVE-2020-16891\",\n \"CVE-2020-16892\",\n \"CVE-2020-16894\",\n \"CVE-2020-16896\",\n \"CVE-2020-16897\",\n \"CVE-2020-16900\",\n \"CVE-2020-16902\",\n \"CVE-2020-16905\",\n \"CVE-2020-16909\",\n \"CVE-2020-16910\",\n \"CVE-2020-16911\",\n \"CVE-2020-16912\",\n \"CVE-2020-16914\",\n \"CVE-2020-16915\",\n \"CVE-2020-16916\",\n \"CVE-2020-16919\",\n \"CVE-2020-16920\",\n \"CVE-2020-16922\",\n \"CVE-2020-16923\",\n \"CVE-2020-16924\",\n \"CVE-2020-16927\",\n \"CVE-2020-16935\",\n \"CVE-2020-16936\",\n \"CVE-2020-16937\",\n \"CVE-2020-16939\",\n \"CVE-2020-16940\",\n \"CVE-2020-16972\",\n \"CVE-2020-16973\",\n \"CVE-2020-16974\",\n \"CVE-2020-16975\",\n \"CVE-2020-16976\",\n \"CVE-2020-16980\"\n );\n script_xref(name:\"MSKB\", value:\"4580346\");\n script_xref(name:\"MSFT\", value:\"MS20-4580346\");\n script_xref(name:\"IAVA\", value:\"2020-A-0457-S\");\n script_xref(name:\"IAVA\", value:\"2020-A-0458-S\");\n\n script_name(english:\"KB4580346: Windows 10 Version 1607 and Windows Server 2016 October 2020 Security Update\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote Windows host is affected by multiple vulnerabilities.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote Windows host is missing security update 4580346.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - A remote code execution vulnerability exists when\n Windows Network Address Translation (NAT) fails to\n properly handle UDP traffic. (CVE-2020-16894)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage VSP Driver improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16885)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-1167, CVE-2020-16923)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage Services improperly handle file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-0764)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16876, CVE-2020-16920)\n\n - A memory corruption vulnerability exists when Windows\n Media Foundation improperly handles objects in memory.\n An attacker who successfully exploited the vulnerability\n could install programs; view, change, or delete data; or\n create new accounts with full user rights. There are\n multiple ways an attacker could exploit the\n vulnerability, such as by convincing a user to open a\n specially crafted document, or by convincing a user to\n visit a malicious webpage. The security update addresses\n the vulnerability by correcting how Windows Media\n Foundation handles objects in memory. (CVE-2020-16915)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - A security feature bypass vulnerability exists when\n Microsoft Windows fails to handle file creation\n permissions, which could allow an attacker to create\n files in a protected Unified Extensible Firmware\n Interface (UEFI) location. (CVE-2020-16910)\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists in\n Windows Error Reporting (WER) when WER handles and\n executes files. The vulnerability could allow elevation\n of privilege if an attacker can successfully exploit it.\n An attacker who successfully exploited the vulnerability\n could gain greater access to sensitive information and\n system functionality. (CVE-2020-16905, CVE-2020-16909)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n specific malicious data from a user on a guest operating\n system. (CVE-2020-1243)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows Backup Service improperly handles file\n operations. (CVE-2020-16912, CVE-2020-16936,\n CVE-2020-16972, CVE-2020-16973, CVE-2020-16974,\n CVE-2020-16975, CVE-2020-16976)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - An information disclosure vulnerability exists when the\n Windows Enterprise App Management Service improperly\n handles certain file operations. An attacker who\n successfully exploited this vulnerability could read\n arbitrary files. An attacker with unprivileged access to\n a vulnerable system could exploit this vulnerability.\n The security update addresses the vulnerability by\n ensuring the Windows Enterprise App Management Service\n properly handles file operations. (CVE-2020-16919)\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4580346\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4580346.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:U/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:U/RL:O/RC:C\");\n script_set_attribute(attribute:\"cvss_score_source\", value:\"CVE-2020-16924\");\n\n script_set_attribute(attribute:\"exploitability_ease\", value:\"No known exploits are available\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2020/10/13\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_copyright(english:\"This script is Copyright (C) 2020 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n\n script_dependencies(\"smb_check_rollup.nasl\", \"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, \"Host/patch_management_checks\");\n\n exit(0);\n}\n\ninclude('smb_func.inc');\ninclude('smb_hotfixes.inc');\ninclude('smb_hotfixes_fcheck.inc');\ninclude('smb_reg_query.inc');\ninclude('install_func.inc');\n\nget_kb_item_or_exit('SMB/MS_Bulletin_Checks/Possible');\n\nbulletin = 'MS20-10';\nkbs = make_list(\n '4580346'\n);\n\nif (get_kb_item('Host/patch_management_checks')) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit('SMB/Registry/Enumerated');\nget_kb_item_or_exit('SMB/WindowsVersion', exit_code:1);\n\nif (hotfix_check_sp_range(win10:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\nshare = hotfix_get_systemdrive(as_share:TRUE, exit_on_fail:TRUE);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n smb_check_rollup(os:'10',\n sp:0,\n os_build:'14393',\n rollup_date:'10_2020',\n bulletin:bulletin,\n rollup_kb_list:[4580346])\n)\n{\n replace_kb_item(name:'SMB/Missing/'+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, hotfix_get_audit_report());\n}\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-11-15T06:24:35", "description": "The remote Windows host is missing security update 4577668.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when\n Windows Error Reporting manager improperly handles a\n process crash. An attacker who successfully exploited\n this vulnerability could delete a targeted file leading\n to an elevated status. (CVE-2020-16895)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage VSP Driver improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16885)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-1167, CVE-2020-16923)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists when the\n Windows TCP/IP stack improperly handles ICMPv6 Router\n Advertisement packets. An attacker who successfully\n exploited this vulnerability could gain the ability to\n execute code on the target server or client.\n (CVE-2020-16898)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage Services improperly handle file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-0764)\n\n - An elevation of privilege vulnerability exists when the\n Windows kernel fails to properly handle objects in\n memory. An attacker who successfully exploited this\n vulnerability could run arbitrary code in kernel mode.\n An attacker could then install programs; view, change,\n or delete data; or create new accounts with full user\n rights. (CVE-2020-16890)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16876, CVE-2020-16920)\n\n - A memory corruption vulnerability exists when Windows\n Media Foundation improperly handles objects in memory.\n An attacker who successfully exploited the vulnerability\n could install programs; view, change, or delete data; or\n create new accounts with full user rights. There are\n multiple ways an attacker could exploit the\n vulnerability, such as by convincing a user to open a\n specially crafted document, or by convincing a user to\n visit a malicious webpage. The security update addresses\n the vulnerability by correcting how Windows Media\n Foundation handles objects in memory. (CVE-2020-16915)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - A security feature bypass vulnerability exists when\n Microsoft Windows fails to handle file creation\n permissions, which could allow an attacker to create\n files in a protected Unified Extensible Firmware\n Interface (UEFI) location. (CVE-2020-16910)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - A denial of service vulnerability exists when the\n Windows TCP/IP stack improperly handles ICMPv6 Router\n Advertisement packets. An attacker who successfully\n exploited this vulnerability could cause a target system\n to stop responding. (CVE-2020-16899)\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists in\n Windows Error Reporting (WER) when WER handles and\n executes files. The vulnerability could allow elevation\n of privilege if an attacker can successfully exploit it.\n An attacker who successfully exploited the vulnerability\n could gain greater access to sensitive information and\n system functionality. (CVE-2020-16905, CVE-2020-16909)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n specific malicious data from a user on a guest operating\n system. (CVE-2020-1243)\n\n - An information disclosure vulnerability exists in Text\n Services Framework when it fails to properly handle\n objects in memory. An attacker who successfully\n exploited this vulnerability could potentially read data\n that was not intended to be disclosed. Note that this\n vulnerability would not allow an attacker to execute\n code or to elevate their user rights directly, but it\n could be used to obtain information that could be used\n to try to further compromise the affected system.\n (CVE-2020-16921)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows Backup Service improperly handles file\n operations. (CVE-2020-16912, CVE-2020-16936,\n CVE-2020-16972, CVE-2020-16973, CVE-2020-16974,\n CVE-2020-16975, CVE-2020-16976)\n\n - An elevation of privilege vulnerability exists in\n Windows when the Windows kernel-mode driver fails to\n properly handle objects in memory. An attacker who\n successfully exploited this vulnerability could run\n arbitrary code in kernel mode. An attacker could then\n install programs; view, change, or delete data; or\n create new accounts with full user rights.\n (CVE-2020-16907, CVE-2020-16913)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - An elevation of privilege vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n handle objects in memory. An attacker who successfully\n exploited these vulnerabilities could gain elevated\n privileges on a target operating system. This\n vulnerability by itself does not allow arbitrary code to\n be run. However, this vulnerability could be used in\n conjunction with one or more vulnerabilities (e.g. a\n remote code execution vulnerability and another\n elevation of privilege) that could take advantage of the\n elevated privileges when running. The update addresses\n the vulnerabilities by correcting how Windows Hyper-V\n handles objects in memory. (CVE-2020-1047,\n CVE-2020-1080)\n\n - An information disclosure vulnerability exists when the\n Windows Enterprise App Management Service improperly\n handles certain file operations. An attacker who\n successfully exploited this vulnerability could read\n arbitrary files. An attacker with unprivileged access to\n a vulnerable system could exploit this vulnerability.\n The security update addresses the vulnerability by\n ensuring the Windows Enterprise App Management Service\n properly handles file operations. (CVE-2020-16919)", "edition": 6, "cvss3": {"score": 7.8, "vector": "AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2020-10-13T00:00:00", "title": "KB4577668: Windows 10 Version 1809 and Windows Server 2019 October 2020 Security Update", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2020-16975", "CVE-2020-1080", "CVE-2020-16905", "CVE-2020-16895", "CVE-2020-16911", "CVE-2020-16889", "CVE-2020-16921", "CVE-2020-16939", "CVE-2020-16972", "CVE-2020-16937", "CVE-2020-16898", "CVE-2020-16974", "CVE-2020-16885", "CVE-2020-16899", "CVE-2020-16891", "CVE-2020-16902", "CVE-2020-16936", "CVE-2020-16892", "CVE-2020-16900", "CVE-2020-16890", "CVE-2020-16927", "CVE-2020-16910", "CVE-2020-16896", "CVE-2020-16909", "CVE-2020-16915", "CVE-2020-16897", "CVE-2020-16976", "CVE-2020-16935", "CVE-2020-16923", "CVE-2020-16907", "CVE-2020-16887", "CVE-2020-16916", "CVE-2020-16924", "CVE-2020-16980", "CVE-2020-16922", "CVE-2020-16940", "CVE-2020-1167", "CVE-2020-16920", "CVE-2020-16912", "CVE-2020-1047", "CVE-2020-16876", "CVE-2020-16913", "CVE-2020-0764", "CVE-2020-1243", "CVE-2020-16914", "CVE-2020-16919", "CVE-2020-16973"], "modified": "2020-10-13T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS20_OCT_4577668.NASL", "href": "https://www.tenable.com/plugins/nessus/141433", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from the Microsoft Security Updates API. The text\n# itself is copyright (C) Microsoft Corporation.\n#\n\ninclude('compat.inc');\n\nif (description)\n{\n script_id(141433);\n script_version(\"1.11\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2020/11/13\");\n\n script_cve_id(\n \"CVE-2020-0764\",\n \"CVE-2020-1047\",\n \"CVE-2020-1080\",\n \"CVE-2020-1167\",\n \"CVE-2020-1243\",\n \"CVE-2020-16876\",\n \"CVE-2020-16885\",\n \"CVE-2020-16887\",\n \"CVE-2020-16889\",\n \"CVE-2020-16890\",\n \"CVE-2020-16891\",\n \"CVE-2020-16892\",\n \"CVE-2020-16895\",\n \"CVE-2020-16896\",\n \"CVE-2020-16897\",\n \"CVE-2020-16898\",\n \"CVE-2020-16899\",\n \"CVE-2020-16900\",\n \"CVE-2020-16902\",\n \"CVE-2020-16905\",\n \"CVE-2020-16907\",\n \"CVE-2020-16909\",\n \"CVE-2020-16910\",\n \"CVE-2020-16911\",\n \"CVE-2020-16912\",\n \"CVE-2020-16913\",\n \"CVE-2020-16914\",\n \"CVE-2020-16915\",\n \"CVE-2020-16916\",\n \"CVE-2020-16919\",\n \"CVE-2020-16920\",\n \"CVE-2020-16921\",\n \"CVE-2020-16922\",\n \"CVE-2020-16923\",\n \"CVE-2020-16924\",\n \"CVE-2020-16927\",\n \"CVE-2020-16935\",\n \"CVE-2020-16936\",\n \"CVE-2020-16937\",\n \"CVE-2020-16939\",\n \"CVE-2020-16940\",\n \"CVE-2020-16972\",\n \"CVE-2020-16973\",\n \"CVE-2020-16974\",\n \"CVE-2020-16975\",\n \"CVE-2020-16976\",\n \"CVE-2020-16980\"\n );\n script_xref(name:\"MSKB\", value:\"4577668\");\n script_xref(name:\"MSFT\", value:\"MS20-4577668\");\n script_xref(name:\"IAVA\", value:\"2020-A-0457-S\");\n script_xref(name:\"IAVA\", value:\"2020-A-0458-S\");\n\n script_name(english:\"KB4577668: Windows 10 Version 1809 and Windows Server 2019 October 2020 Security Update\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote Windows host is affected by multiple vulnerabilities.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote Windows host is missing security update 4577668.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A spoofing vulnerability exists when Windows incorrectly\n validates file signatures. An attacker who successfully\n exploited this vulnerability could bypass security\n features and load improperly signed files. In an attack\n scenario, an attacker could bypass security features\n intended to prevent improperly signed files from being\n loaded. The update addresses the vulnerability by\n correcting how Windows validates file signatures.\n (CVE-2020-16922)\n\n - An elevation of privilege vulnerability exists when\n Windows Error Reporting manager improperly handles a\n process crash. An attacker who successfully exploited\n this vulnerability could delete a targeted file leading\n to an elevated status. (CVE-2020-16895)\n\n - A remote code execution vulnerability exists when the\n Windows Jet Database Engine improperly handles objects\n in memory. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on a victim\n system. An attacker could exploit this vulnerability by\n enticing a victim to open a specially crafted file. The\n update addresses the vulnerability by correcting the way\n the Windows Jet Database Engine handles objects in\n memory. (CVE-2020-16924)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage VSP Driver improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16885)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft Graphics Components handle objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute arbitrary code on a target\n system. (CVE-2020-1167, CVE-2020-16923)\n\n - A remote code execution vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n validate input from an authenticated user on a guest\n operating system. (CVE-2020-16891)\n\n - A remote code execution vulnerability exists when the\n Windows TCP/IP stack improperly handles ICMPv6 Router\n Advertisement packets. An attacker who successfully\n exploited this vulnerability could gain the ability to\n execute code on the target server or client.\n (CVE-2020-16898)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows kernel image handles objects in\n memory. An attacker who successfully exploited the\n vulnerability could execute code with elevated\n permissions. (CVE-2020-16892)\n\n - An information disclosure vulnerability exists in the\n way that the Windows Graphics Device Interface Plus\n (GDI+) handles objects in memory, allowing an attacker\n to retrieve information from a targeted system. By\n itself, the information disclosure does not allow\n arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability.\n (CVE-2020-16914)\n\n - An elevation of privilege vulnerability exists in the\n Windows Installer when the Windows Installer fails to\n properly sanitize input leading to an insecure library\n loading behavior. A locally authenticated attacker could\n run arbitrary code with elevated system privileges. An\n attacker could then install programs; view, change, or\n delete data; or create new accounts with full user\n rights. The security update addresses the vulnerability\n by correcting the input sanitization error to preclude\n unintended elevation. (CVE-2020-16902)\n\n - An elevation of privilege vulnerability exists when the\n Windows Storage Services improperly handle file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-0764)\n\n - An elevation of privilege vulnerability exists when the\n Windows kernel fails to properly handle objects in\n memory. An attacker who successfully exploited this\n vulnerability could run arbitrary code in kernel mode.\n An attacker could then install programs; view, change,\n or delete data; or create new accounts with full user\n rights. (CVE-2020-16890)\n\n - An information disclosure vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16896)\n\n - A remote code execution vulnerability exists in the way\n that the Windows Graphics Device Interface (GDI) handles\n objects in the memory. An attacker who successfully\n exploited this vulnerability could take control of the\n affected system. An attacker could then install\n programs; view, change, or delete data; or create new\n accounts with full user rights. (CVE-2020-16911)\n\n - An information disclosure vulnerability exists when\n NetBIOS over TCP (NBT) Extensions (NetBT) improperly\n handle objects in memory. An attacker who successfully\n exploited this vulnerability could obtain information to\n further compromise the users system. (CVE-2020-16897)\n\n - An elevation of privilege vulnerability exists when the\n Windows Application Compatibility Client Library\n improperly handles registry operations. An attacker who\n successfully exploited this vulnerability could gain\n elevated privileges. (CVE-2020-16876, CVE-2020-16920)\n\n - A memory corruption vulnerability exists when Windows\n Media Foundation improperly handles objects in memory.\n An attacker who successfully exploited the vulnerability\n could install programs; view, change, or delete data; or\n create new accounts with full user rights. There are\n multiple ways an attacker could exploit the\n vulnerability, such as by convincing a user to open a\n specially crafted document, or by convincing a user to\n visit a malicious webpage. The security update addresses\n the vulnerability by correcting how Windows Media\n Foundation handles objects in memory. (CVE-2020-16915)\n\n - An elevation of privilege vulnerability exists when the\n Windows User Profile Service (ProfSvc) improperly\n handles junction points. An attacker who successfully\n exploited this vulnerability could delete files and\n folders in an elevated context. (CVE-2020-16940)\n\n - A security feature bypass vulnerability exists when\n Microsoft Windows fails to handle file creation\n permissions, which could allow an attacker to create\n files in a protected Unified Extensible Firmware\n Interface (UEFI) location. (CVE-2020-16910)\n\n - A denial of service vulnerability exists in Remote\n Desktop Protocol (RDP) when an attacker connects to the\n target system using RDP and sends specially crafted\n requests. An attacker who successfully exploited this\n vulnerability could cause the RDP service on the target\n system to stop responding. (CVE-2020-16927)\n\n - A denial of service vulnerability exists when the\n Windows TCP/IP stack improperly handles ICMPv6 Router\n Advertisement packets. An attacker who successfully\n exploited this vulnerability could cause a target system\n to stop responding. (CVE-2020-16899)\n\n - An elevation of privilege vulnerability exists when\n Group Policy improperly checks access. An attacker who\n successfully exploited this vulnerability could run\n processes in an elevated context. (CVE-2020-16939)\n\n - An elevation of privilege vulnerability exists in\n Windows Error Reporting (WER) when WER handles and\n executes files. The vulnerability could allow elevation\n of privilege if an attacker can successfully exploit it.\n An attacker who successfully exploited the vulnerability\n could gain greater access to sensitive information and\n system functionality. (CVE-2020-16905, CVE-2020-16909)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n specific malicious data from a user on a guest operating\n system. (CVE-2020-1243)\n\n - An information disclosure vulnerability exists in Text\n Services Framework when it fails to properly handle\n objects in memory. An attacker who successfully\n exploited this vulnerability could potentially read data\n that was not intended to be disclosed. Note that this\n vulnerability would not allow an attacker to execute\n code or to elevate their user rights directly, but it\n could be used to obtain information that could be used\n to try to further compromise the affected system.\n (CVE-2020-16921)\n\n - An elevation of privilege vulnerability exists in the\n way that the Windows Network Connections Service handles\n objects in memory. An attacker who successfully\n exploited the vulnerability could execute code with\n elevated permissions. (CVE-2020-16887)\n\n - An elevation of privilege vulnerability exists when the\n Windows Backup Service improperly handles file\n operations. (CVE-2020-16912, CVE-2020-16936,\n CVE-2020-16972, CVE-2020-16973, CVE-2020-16974,\n CVE-2020-16975, CVE-2020-16976)\n\n - An elevation of privilege vulnerability exists in\n Windows when the Windows kernel-mode driver fails to\n properly handle objects in memory. An attacker who\n successfully exploited this vulnerability could run\n arbitrary code in kernel mode. An attacker could then\n install programs; view, change, or delete data; or\n create new accounts with full user rights.\n (CVE-2020-16907, CVE-2020-16913)\n\n - An information disclosure vulnerability exists when the\n .NET Framework improperly handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could disclose contents of an affected system's memory.\n (CVE-2020-16937)\n\n - An information disclosure vulnerability exists when the\n Windows KernelStream improperly handles objects in\n memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2020-16889)\n\n - An elevation of privilege vulnerability exists when the\n Windows iSCSI Target Service improperly handles file\n operations. An attacker who successfully exploited this\n vulnerability could gain elevated privileges.\n (CVE-2020-16980)\n\n - An elevation of privilege vulnerability exists when\n Windows improperly handles COM object creation. An\n attacker who successfully exploited the vulnerability\n could run arbitrary code with elevated privileges.\n (CVE-2020-16916, CVE-2020-16935)\n\n - An elevation of privilege vulnerability exists when the\n Windows Event System improperly handles objects in\n memory. (CVE-2020-16900)\n\n - An elevation of privilege vulnerability exists when\n Windows Hyper-V on a host server fails to properly\n handle objects in memory. An attacker who successfully\n exploited these vulnerabilities could gain elevated\n privileges on a target operating system. This\n vulnerability by itself does not allow arbitrary code to\n be run. However, this vulnerability could be used in\n conjunction with one or more vulnerabilities (e.g. a\n remote code execution vulnerability and another\n elevation of privilege) that could take advantage of the\n elevated privileges when running. The update addresses\n the vulnerabilities by correcting how Windows Hyper-V\n handles objects in memory. (CVE-2020-1047,\n CVE-2020-1080)\n\n - An information disclosure vulnerability exists when the\n Windows Enterprise App Management Service improperly\n handles certain file operations. An attacker who\n successfully exploited this vulnerability could read\n arbitrary files. An attacker with unprivileged access to\n a vulnerable system could exploit this vulnerability.\n The security update addresses the vulnerability by\n ensuring the Windows Enterprise App Management Service\n properly handles file operations. (CVE-2020-16919)\");\n script_set_attribute(attribute:\"see_also\", value:\"https://support.microsoft.com/en-us/help/4577668\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4577668.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:H/RL:O/RC:C\");\n script_set_attribute(attribute:\"cvss_score_source\", value:\"CVE-2020-16924\");\n\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2020/10/13\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2020/10/13\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_copyright(english:\"This script is Copyright (C) 2020 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n\n script_dependencies(\"smb_check_rollup.nasl\", \"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, \"Host/patch_management_checks\");\n\n exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_func.inc\");\ninclude(\"misc_func.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = \"MS20-10\";\nkbs = make_list('4577668');\n\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit(\"SMB/Registry/Enumerated\");\nget_kb_item_or_exit(\"SMB/WindowsVersion\", exit_code:1);\n\nif (hotfix_check_sp_range(win10:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\nshare = hotfix_get_systemdrive(as_share:TRUE, exit_on_fail:TRUE);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n smb_check_rollup(os:\"10\",\n sp:0,\n os_build:\"17763\",\n rollup_date:\"10_2020\",\n bulletin:bulletin,\n rollup_kb_list:[4577668])\n)\n{\n replace_kb_item(name:'SMB/Missing/'+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, hotfix_get_audit_report());\n}\n\n\n\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "kaspersky": [{"lastseen": "2020-12-03T07:10:10", "bulletinFamily": "info", "cvelist": ["CVE-2020-16975", "CVE-2020-16901", "CVE-2020-1080", "CVE-2020-16905", "CVE-2020-16895", "CVE-2020-16911", "CVE-2020-16889", "CVE-2020-16921", "CVE-2020-16939", "CVE-2020-16972", "CVE-2020-16898", "CVE-2020-16974", "CVE-2020-16968", "CVE-2020-16885", "CVE-2020-16938", "CVE-2020-16899", "CVE-2020-16891", "CVE-2020-16902", "CVE-2020-16936", "CVE-2020-16892", "CVE-2020-16900", "CVE-2020-16890", "CVE-2020-16927", "CVE-2020-16910", "CVE-2020-16896", "CVE-2020-16909", "CVE-2020-16915", "CVE-2020-16897", "CVE-2020-16976", "CVE-2020-16935", "CVE-2020-16923", "CVE-2020-16907", "CVE-2020-16887", "CVE-2020-16916", "CVE-2020-16894", "CVE-2020-16924", "CVE-2020-16877", "CVE-2020-16980", "CVE-2020-16967", "CVE-2020-16922", "CVE-2020-16940", "CVE-2020-1167", "CVE-2020-16920", "CVE-2020-16912", "CVE-2020-1047", "CVE-2020-16876", "CVE-2020-16913", "CVE-2020-0764", "CVE-2020-1243", "CVE-2020-16914", "CVE-2020-16908", "CVE-2020-16919", "CVE-2020-16973"], "description": "### *Detect date*:\n10/13/2020\n\n### *Severity*:\nCritical\n\n### *Description*:\nMultiple vulnerabilities were found in Microsoft Windows. Malicious users can exploit these vulnerabilities to execute arbitrary code, obtain sensitive information, gain privileges, spoof user interface, cause denial of service, bypass security restrictions.\n\n### *Exploitation*:\nMalware exists for this vulnerability. Usually such malware is classified as Exploit. [More details](<https://threats.kaspersky.com/en/class/Exploit/>).\n\n### *Affected products*:\nWindows 10 Version 1809 for x64-based Systems \nWindows 10 Version 2004 for x64-based Systems \nWindows 10 Version 1909 for ARM64-based Systems \nWindows Server, version 1903 (Server Core installation) \nWindows Server 2012 (Server Core installation) \nWindows 10 Version 1607 for x64-based Systems \nWindows 10 Version 1909 for x64-based Systems \nWindows 10 Version 1903 for ARM64-based Systems \nWindows Server 2019 (Server Core installation) \nWindows 10 for 32-bit Systems \nWindows Server 2012 R2 \nWindows Server 2016 (Server Core installation) \nWindows 10 Version 2004 for 32-bit Systems \nWindows 10 Version 1803 for x64-based Systems \nWindows 10 Version 1809 for ARM64-based Systems \nWindows RT 8.1 \nWindows Server 2008 R2 for x64-based Systems Service Pack 1 \nWindows Server 2012 R2 (Server Core installation) \nWindows 10 Version 2004 for ARM64-based Systems \nWindows Server 2012 \nWindows Server 2016 \nWindows 8.1 for x64-based systems \nWindows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) \nWindows 7 for x64-based Systems Service Pack 1 \nWindows 10 Version 1803 for ARM64-based Systems \nWindows 10 Version 1709 for 32-bit Systems \nWindows 10 for x64-based Systems \nWindows 7 for 32-bit Systems Service Pack 1 \nWindows 10 Version 1607 for 32-bit Systems \nWindows Server 2008 for 32-bit Systems Service Pack 2 \nWindows 8.1 for 32-bit systems \nWindows Server, version 2004 (Server Core installation) \nWindows 10 Version 1903 for 32-bit Systems \nWindows 10 Version 1709 for ARM64-based Systems \nWindows Server 2008 for x64-based Systems Service Pack 2 \nWindows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) \nWindows 10 Version 1709 for x64-based Systems \nWindows 10 Version 1903 for x64-based Systems \nWindows 10 Version 1809 for 32-bit Systems \nWindows Server, version 1909 (Server Core installation) \nWindows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) \nWindows 10 Version 1803 for 32-bit Systems \nWindows 10 Version 1909 for 32-bit Systems \nWindows Server 2019\n\n### *Solution*:\nInstall necessary updates from the KB section, that are listed in your Windows Update (Windows Update usually can be accessed from the Control Panel)\n\n### *Original advisories*:\n[CVE-2020-16923](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16923>) \n[CVE-2020-16889](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16889>) \n[CVE-2020-16887](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16887>) \n[CVE-2020-16902](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16902>) \n[CVE-2020-16885](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16885>) \n[CVE-2020-16898](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16898>) \n[CVE-2020-16968](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16968>) \n[CVE-2020-16939](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16939>) \n[CVE-2020-16980](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16980>) \n[CVE-2020-16972](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16972>) \n[CVE-2020-16967](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16967>) \n[CVE-2020-16876](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16876>) \n[CVE-2020-16919](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16919>) \n[CVE-2020-16940](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16940>) \n[CVE-2020-16908](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16908>) \n[CVE-2020-16909](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16909>) \n[CVE-2020-16920](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16920>) \n[CVE-2020-16907](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16907>) \n[CVE-2020-16922](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16922>) \n[CVE-2020-16905](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16905>) \n[CVE-2020-16924](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16924>) \n[CVE-2020-1243](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-1243>) \n[CVE-2020-16900](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16900>) \n[CVE-2020-16927](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16927>) \n[CVE-2020-0764](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-0764>) \n[CVE-2020-16890](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16890>) \n[CVE-2020-16891](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16891>) \n[CVE-2020-16892](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16892>) \n[CVE-2020-16894](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16894>) \n[CVE-2020-16901](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16901>) \n[CVE-2020-16896](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16896>) \n[CVE-2020-16897](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16897>) \n[CVE-2020-16973](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16973>) \n[CVE-2020-16899](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16899>) \n[CVE-2020-1047](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-1047>) \n[CVE-2020-16976](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16976>) \n[CVE-2020-16975](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16975>) \n[CVE-2020-16974](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16974>) \n[CVE-2020-16936](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16936>) \n[CVE-2020-16935](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16935>) \n[CVE-2020-1167](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-1167>) \n[CVE-2020-16877](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16877>) \n[CVE-2020-16912](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16912>) \n[CVE-2020-1080](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-1080>) \n[CVE-2020-16914](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16914>) \n[CVE-2020-16916](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16916>) \n[CVE-2020-16911](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16911>) \n[CVE-2020-16910](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16910>) \n[CVE-2020-16913](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16913>) \n[CVE-2020-16938](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16938>) \n[CVE-2020-16915](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16915>) \n[CVE-2020-16921](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16921>) \n[CVE-2020-16895](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2020-16895>) \n\n\n### *Impacts*:\nACE \n\n### *Related products*:\n[Microsoft Windows](<https://threats.kaspersky.com/en/product/Microsoft-Windows/>)\n\n### *CVE-IDS*:\n[CVE-2020-16923](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16923>)6.8High \n[CVE-2020-16889](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16889>)5.0Critical \n[CVE-2020-16887](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16887>)5.0Critical \n[CVE-2020-16902](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16902>)5.0Critical \n[CVE-2020-16885](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16885>)5.0Critical \n[CVE-2020-16898](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16898>)5.0Critical \n[CVE-2020-16968](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16968>)5.0Critical \n[CVE-2020-16939](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16939>)4.6Warning \n[CVE-2020-16980](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16980>)4.6Warning \n[CVE-2020-16972](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16972>)4.6Warning \n[CVE-2020-16967](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16967>)9.3Critical \n[CVE-2020-16876](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16876>)4.6Warning \n[CVE-2020-16919](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16919>)2.1Warning \n[CVE-2020-16940](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16940>)4.9Warning \n[CVE-2020-16908](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16908>)7.2High \n[CVE-2020-16909](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16909>)4.6Warning \n[CVE-2020-16920](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16920>)4.6Warning \n[CVE-2020-16907](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16907>)7.2High \n[CVE-2020-16922](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16922>)2.1Warning \n[CVE-2020-16905](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16905>)4.6Warning \n[CVE-2020-16924](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16924>)9.3Critical \n[CVE-2020-1243](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1243>)4.6Warning \n[CVE-2020-16900](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16900>)5.0Critical \n[CVE-2020-16927](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16927>)5.0Critical \n[CVE-2020-0764](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0764>)4.6Warning \n[CVE-2020-16890](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16890>)5.0Critical \n[CVE-2020-16891](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16891>)5.0Critical \n[CVE-2020-16892](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16892>)5.0Critical \n[CVE-2020-16894](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16894>)6.8High \n[CVE-2020-16901](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16901>)2.1Warning \n[CVE-2020-16896](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16896>)5.0Critical \n[CVE-2020-16897](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16897>)2.1Warning \n[CVE-2020-16973](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16973>)4.6Warning \n[CVE-2020-16899](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16899>)7.8Critical \n[CVE-2020-1047](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1047>)7.2High \n[CVE-2020-16976](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16976>)4.6Warning \n[CVE-2020-16975](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16975>)4.6Warning \n[CVE-2020-16974](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16974>)4.6Warning \n[CVE-2020-16936](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16936>)4.6Warning \n[CVE-2020-16935](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16935>)7.2High \n[CVE-2020-1167](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1167>)9.3Critical \n[CVE-2020-16877](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16877>)3.6Warning \n[CVE-2020-16912](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16912>)4.6Warning \n[CVE-2020-1080](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1080>)7.2High \n[CVE-2020-16914](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16914>)2.1Warning \n[CVE-2020-16916](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16916>)5.0Critical \n[CVE-2020-16911](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16911>)9.3Critical \n[CVE-2020-16910](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16910>)4.3Warning \n[CVE-2020-16913](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16913>)7.2High \n[CVE-2020-16938](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16938>)2.1Warning \n[CVE-2020-16915](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16915>)6.8High \n[CVE-2020-16921](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16921>)2.1Warning \n[CVE-2020-16895](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16895>)7.2High\n\n### *KB list*:\n[4577041](<http://support.microsoft.com/kb/4577041>) \n[4577049](<http://support.microsoft.com/kb/4577049>) \n[4580328](<http://support.microsoft.com/kb/4580328>) \n[4580330](<http://support.microsoft.com/kb/4580330>) \n[4580327](<http://support.microsoft.com/kb/4580327>) \n[4580346](<http://support.microsoft.com/kb/4580346>) \n[4579311](<http://support.microsoft.com/kb/4579311>) \n[4580353](<http://support.microsoft.com/kb/4580353>) \n[4580347](<http://support.microsoft.com/kb/4580347>) \n[4580382](<http://support.microsoft.com/kb/4580382>) \n[4580358](<http://support.microsoft.com/kb/4580358>) \n[4577668](<http://support.microsoft.com/kb/4577668>) \n[4577671](<http://support.microsoft.com/kb/4577671>)\n\n### *Microsoft official advisories*:", "edition": 3, "modified": "2020-11-19T00:00:00", "published": "2020-10-13T00:00:00", "id": "KLA11977", "href": "https://threats.kaspersky.com/en/vulnerability/KLA11977", "title": "\r KLA11977Multiple vulnerabilities in Microsoft Windows ", "type": "kaspersky", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}]}