{"id": "MS:CVE-2019-1128", "bulletinFamily": "microsoft", "title": "DirectWrite Remote Code Execution Vulnerability", "description": "A remote code execution vulnerability exists in the way that DirectWrite handles objects in memory. An attacker who successfully exploited this vulnerability could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.\n\nThere are multiple ways an attacker could exploit the vulnerability, such as by convincing a user to open a specially crafted document, or by convincing a user to visit an untrusted webpage.\n\nThe security update addresses the vulnerability by correcting how DirectWrite handles objects in memory.\n", "published": "2019-07-09T07:00:00", "modified": "2019-07-09T07:00:00", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}, "href": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1128", "reporter": "Microsoft", "references": [], "cvelist": ["CVE-2019-1128"], "type": "mscve", "lastseen": "2020-08-07T11:48:29", "edition": 2, "viewCount": 0, "enchantments": {"dependencies": {"references": [{"type": "cve", "idList": ["CVE-2019-1128"]}, {"type": "symantec", "idList": ["SMNTC-108943"]}, {"type": "exploitdb", "idList": ["EDB-ID:47095"]}, {"type": "kaspersky", "idList": ["KLA11511"]}, {"type": "nessus", "idList": ["SMB_NT_MS19_JUL_4507469.NASL", "SMB_NT_MS19_JUL_4507453.NASL", "SMB_NT_MS19_JUL_4507455.NASL", "SMB_NT_MS19_JUL_4507435.NASL"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310815401", "OPENVAS:1361412562310815408", "OPENVAS:1361412562310815400", "OPENVAS:1361412562310815410"]}, {"type": "talosblog", "idList": ["TALOSBLOG:07D81B04EFE21AC0E3C8DD9F1F76E7A4"]}], "modified": "2020-08-07T11:48:29", "rev": 2}, "score": {"value": 7.2, "vector": "NONE", "modified": "2020-08-07T11:48:29", "rev": 2}, "vulnersScore": 7.2}, "kbList": ["KB4503286", "KB4503293", "KB4507435", "KB4507455", "KB4503327", "KB4503284", "KB4507453", "KB4507469"], "msrc": "", "mscve": "CVE-2019-1128", "msAffectedSoftware": [{"kb": "KB4507455", "kbSupersedence": "KB4503284", "msplatform": "", "name": "Windows 10 Version 1709 for ARM64-based Systems"}, {"kb": "KB4507435", "kbSupersedence": "KB4503286", "msplatform": "", "name": "Windows Server, version 1803 (Server Core Installation)"}, {"kb": "KB4507453", "kbSupersedence": "KB4503293", "msplatform": "", "name": "Windows Server, version 1903 (Server Core installation)"}, {"kb": "KB4507453", "kbSupersedence": "KB4503293", "msplatform": "", "name": "Windows 10 Version 1903 for ARM64-based Systems"}, {"kb": "KB4507469", "kbSupersedence": "KB4503327", "msplatform": "", "name": "Windows Server 2019 (Server Core installation)"}, {"kb": "KB4507435", "kbSupersedence": "KB4503286", "msplatform": "", "name": "Windows 10 Version 1803 for 32-bit Systems"}, {"kb": "KB4507469", "kbSupersedence": "KB4503327", "msplatform": "", "name": "Windows Server 2019"}, {"kb": "KB4507455", "kbSupersedence": "KB4503284", "msplatform": "", "name": "Windows 10 Version 1709 for x64-based Systems"}, {"kb": "KB4507469", "kbSupersedence": "KB4503327", "msplatform": "", "name": "Windows 10 Version 1809 for x64-based Systems"}, {"kb": "KB4507469", "kbSupersedence": "KB4503327", "msplatform": "", "name": "Windows 10 Version 1809 for 32-bit Systems"}, {"kb": "KB4507435", "kbSupersedence": "KB4503286", "msplatform": "", "name": "Windows 10 Version 1803 for x64-based Systems"}, {"kb": "KB4507435", "kbSupersedence": "KB4503286", "msplatform": "", "name": "Windows 10 Version 1803 for ARM64-based Systems"}, {"kb": "KB4507455", "kbSupersedence": "KB4503284", "msplatform": "", "name": "Windows 10 Version 1709 for 32-bit Systems"}, {"kb": "KB4507453", "kbSupersedence": "KB4503293", "msplatform": "", "name": "Windows 10 Version 1903 for 32-bit Systems"}, {"kb": "KB4507469", "kbSupersedence": "KB4503327", "msplatform": "", "name": "Windows 10 Version 1809 for ARM64-based Systems"}, {"kb": "KB4507453", "kbSupersedence": "KB4503293", "msplatform": "", "name": "Windows 10 Version 1903 for x64-based Systems"}], "scheme": null}

{"cve": [{"lastseen": "2021-02-02T07:12:48", "description": "A remote code execution vulnerability exists in the way that DirectWrite handles objects in memory, aka 'DirectWrite Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1117, CVE-2019-1118, CVE-2019-1119, CVE-2019-1120, CVE-2019-1121, CVE-2019-1122, CVE-2019-1123, CVE-2019-1124, CVE-2019-1127.", "edition": 6, "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "baseScore": 8.8, "privilegesRequired": "NONE", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "userInteraction": "REQUIRED", "version": "3.0"}, "impactScore": 5.9}, "published": "2019-07-15T19:15:00", "title": "CVE-2019-1128", "type": "cve", "cwe": ["NVD-CWE-noinfo"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 9.3, "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "acInsufInfo": false, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2019-1128"], "modified": "2020-08-24T17:37:00", "cpe": ["cpe:/o:microsoft:windows_server_2019:-", "cpe:/o:microsoft:windows_10:1803", "cpe:/o:microsoft:windows_server_2016:1803", "cpe:/o:microsoft:windows_10:1903", "cpe:/o:microsoft:windows_10:1709", "cpe:/o:microsoft:windows_10:1809", "cpe:/o:microsoft:windows_server_2016:1903"], "id": "CVE-2019-1128", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-1128", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:1903:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_10:1809:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_10:1709:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_10:1903:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_10:1803:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_server_2016:1803:*:*:*:*:*:*:*"]}], "symantec": [{"lastseen": "2019-07-10T00:40:12", "bulletinFamily": "software", "cvelist": ["CVE-2019-1128"], "description": "### Description\n\nMicrosoft Windows is prone to a remote code-execution vulnerability. An attacker can leverage this issue to execute arbitrary code in the context of the currently logged-in user. Failed exploit attempts will likely result in denial of service conditions.\n\n### Technologies Affected\n\n * Microsoft Windows 10 Version 1709 for ARM64-based Systems \n * Microsoft Windows 10 Version 1803 for 32-bit Systems \n * Microsoft Windows 10 Version 1803 for ARM64-based Systems \n * Microsoft Windows 10 Version 1803 for x64-based Systems \n * Microsoft Windows 10 Version 1809 for 32-bit Systems \n * Microsoft Windows 10 Version 1809 for ARM64-based Systems \n * Microsoft Windows 10 Version 1809 for x64-based Systems \n * Microsoft Windows 10 Version 1903 for 32-bit Systems \n * Microsoft Windows 10 Version 1903 for ARM64-based Systems \n * Microsoft Windows 10 Version 1903 for x64-based Systems \n * Microsoft Windows 10 version 1709 for 32-bit Systems \n * Microsoft Windows 10 version 1709 for x64-based Systems \n * Microsoft Windows Server 1803 \n * Microsoft Windows Server 1903 \n * Microsoft Windows Server 2019 \n\n### Recommendations\n\n**Block external access at the network boundary, unless external parties require service.** \nIf global access isn't needed, block access at the network perimeter to computers hosting the vulnerable operating system.\n\n**Deploy network intrusion detection systems to monitor network traffic for malicious activity.** \nDeploy NIDS to monitor network traffic for signs of anomalous or suspicious activity such as unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.\n\n**Communicate sensitive information through secure means.** \nImplement multiple layers of encryption and authentication to help mitigate against exposure from this and other latent vulnerabilities.\n\nUpdates are available. Please see the references or vendor advisory for more information.\n", "modified": "2019-07-09T00:00:00", "published": "2019-07-09T00:00:00", "id": "SMNTC-108943", "href": "https://www.symantec.com/content/symantec/english/en/security-center/vulnerabilities/writeup.html/108943", "type": "symantec", "title": "Microsoft Windows 'DirectWrite' API CVE-2019-1128 Remote Code Execution Vulnerability", "cvss": {"score": 0.0, "vector": "NONE"}}], "exploitdb": [{"lastseen": "2019-07-10T15:32:02", "description": "", "published": "2019-07-10T00:00:00", "type": "exploitdb", "title": "Microsoft DirectWrite / AFDKO - Heap-Based Buffer Overflow in OpenType Font Handling in readCharset", "bulletinFamily": "exploit", "cvelist": ["CVE-2019-1128"], "modified": "2019-07-10T00:00:00", "id": "EDB-ID:47095", "href": "https://www.exploit-db.com/exploits/47095", "sourceData": "-----=====[ Background ]=====-----\r\n\r\nAFDKO (Adobe Font Development Kit for OpenType) is a set of tools for examining, modifying and building fonts. The core part of this toolset is a font handling library written in C, which provides interfaces for reading and writing Type 1, OpenType, TrueType (to some extent) and several other font formats. While the library existed as early as 2000, it was open-sourced by Adobe in 2014 on GitHub [1, 2], and is still actively developed. The font parsing code can be generally found under afdko/c/public/lib/source/*read/*.c in the project directory tree.\r\n\r\nAt the time of this writing, based on the available source code, we conclude that AFDKO was originally developed to only process valid, well-formatted font files. It contains very few to no sanity checks of the input data, which makes it susceptible to memory corruption issues (e.g. buffer overflows) and other memory safety problems, if the input file doesn't conform to the format specification.\r\n\r\nWe have recently discovered that starting with Windows 10 1709 (Fall Creators Update, released in October 2017), Microsoft's DirectWrite library [3] includes parts of AFDKO, and specifically the modules for reading and writing OpenType/CFF fonts (internally called cfr/cfw). The code is reachable through dwrite!AdobeCFF2Snapshot, called by methods of the FontInstancer class, called by dwrite!DWriteFontFace::CreateInstancedStream and dwrite!DWriteFactory::CreateInstancedStream. This strongly indicates that the code is used for instancing the relatively new variable fonts [4], i.e. building a single instance of a variable font with a specific set of attributes. The CreateInstancedStream method is not a member of a public COM interface, but we have found that it is called by d2d1!dxc::TextConvertor::InstanceFontResources, which led us to find out that it can be reached through the Direct2D printing interface. It is unclear if there are other ways to trigger the font instancing functionality.\r\n\r\nOne example of a client application which uses Direct2D printing is Microsoft Edge. If a user opens a specially crafted website with an embedded OpenType variable font and decides to print it (to PDF, XPS, or another physical or virtual printer), the AFDKO code will execute with the attacker's font file as input. Below is a description of one such security vulnerability in Adobe's library exploitable through the Edge web browser.\r\n\r\n-----=====[ Description ]=====-----\r\n\r\nThe readCharset() function in afdko/c/public/lib/source/cffread/cffread.c is designed to read and parse the charset information of an input OpenType font. It is called by cfrBegFont(), the standard entry point function for the \"cfr\" (CFF Reader) module of AFDKO. The relevant part of the function is shown below:\r\n\r\n--- cut ---\r\n[...]\r\n 2179 case 1:\r\n 2180 size = 1;\r\n 2181 /* Fall through */\r\n 2182 case 2:\r\n 2183 while (gid < h->glyphs.cnt) {\r\n 2184 unsigned short id = read2(h);\r\n 2185 long nLeft = readN(h, size);\r\n 2186 while (nLeft-- >= 0)\r\n 2187 addID(h, gid++, id++);\r\n 2188 }\r\n 2189 break;\r\n--- cut ---\r\n\r\nwhereas addID() is defined as follows:\r\n\r\n--- cut ---\r\n 1838 /* Add SID/CID to charset */\r\n 1839 static void addID(cfrCtx h, long gid, unsigned short id) {\r\n 1840 abfGlyphInfo *info = &h->glyphs.array[gid];\r\n 1841 if (h->flags & CID_FONT)\r\n 1842 /* Save CID */\r\n 1843 info->cid = id;\r\n 1844 else {\r\n 1845 /* Save SID */\r\n 1846 info->gname.impl = id;\r\n 1847 info->gname.ptr = sid2str(h, id);\r\n 1848\r\n 1849 /* Non-CID font so select FD[0] */\r\n 1850 info->iFD = 0;\r\n[...]\r\n 1859 }\r\n 1860 }\r\n--- cut ---\r\n\r\nThe readCharset() routine doesn't consider the size of the h->glyphs array and writes to it solely based on the charset information. If the value read from the input stream in line 2185 exceeds the number of glyphs in the font, the array may be overflown in addID() (line 1843 or 1846, 1847, 1850), corrupting adjacent objects on the heap. The h->glyphs array is initialized in readCharStringsINDEX() according to the number of CharStrings found in the font:\r\n\r\n--- cut ---\r\n 1791 dnaSET_CNT(h->glyphs, index.count);\r\n--- cut ---\r\n\r\n-----=====[ Proof of Concept ]=====-----\r\n\r\nThe proof of concept font contains a charset descriptor with the following initial values:\r\n\r\n- width = 0x02 (changed from 0x01)\r\n- id = 0x4141 (changed from 0x0001)\r\n- nLeft = 0xffff (changed from 0x15)\r\n\r\nBy increasing the value of \"nLeft\" from 21 to 65535, we cause the loop in lines 2386-2387 to go largely out of bounds and overflow the h->glyphs array.\r\n\r\nIn theory, the vulnerability shouldn't be possible to reach in Microsoft DirectWrite and its client applications, because AFDKO is only used there for instancing variable fonts, whereas such CFF2 fonts follow another execution path in the readCharset() function:\r\n\r\n--- cut ---\r\n 2138 if (h->header.major == 2) {\r\n 2139 postRead(h);\r\n 2140 if (h->cff2.mvar)\r\n 2141 MVARread(h);\r\n 2142 if (!(h->flags & CID_FONT))\r\n 2143 readCharSetFromPost(h);\r\n 2144 else {\r\n 2145 long gid;\r\n 2146 for (gid = 0; gid < h->glyphs.cnt; gid++) {\r\n 2147 abfGlyphInfo *info = &h->glyphs.array[gid];\r\n 2148 info->cid = (unsigned short)gid;\r\n 2149 }\r\n 2150 }\r\n 2151 return;\r\n 2152 }\r\n--- cut ---\r\n\r\nHowever, we have found that it is in fact possible to trigger the handling of CFFv1 in AFDKO, by appending the old style \"CFF \" table to a variable font which already includes a \"CFF2\" one. This causes DirectWrite to correctly load the variable font, but AFDKO still finds \"CFF \" first and passes it for further parsing, thanks to the following logic in srcOpen() (afdko/c/public/lib/source/cffread/cffread.c):\r\n\r\n--- cut ---\r\n 561 /* OTF; use CFF table offset */\r\n 562 sfrTable *table =\r\n 563 sfrGetTableByTag(h->ctx.sfr, CTL_TAG('C', 'F', 'F', ' '));\r\n 564 if (table == NULL) {\r\n 565 table = sfrGetTableByTag(h->ctx.sfr, CTL_TAG('C', 'F', 'F', '2'));\r\n 566 }\r\n 567 if (table == NULL)\r\n 568 fatal(h, cfrErrNoCFF);\r\n 569 origin = table->offset;\r\n--- cut ---\r\n\r\n-----=====[ Crash logs ]=====-----\r\n\r\nA 64-bit build of \"tx\" compiled with AddressSanitizer, started with ./tx -cff poc.otf prints out the following report:\r\n\r\n--- cut ---\r\n=================================================================\r\n==236657==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62a00000b228 at pc 0x0000005563be bp 0x7ffe3c238d10 sp 0x7ffe3c238d08\r\nWRITE of size 2 at 0x62a00000b228 thread T0\r\n #0 0x5563bd in addID afdko/c/public/lib/source/cffread/cffread.c:1843:19\r\n #1 0x53f71c in readCharset afdko/c/public/lib/source/cffread/cffread.c:2187:29\r\n #2 0x5299c7 in cfrBegFont afdko/c/public/lib/source/cffread/cffread.c:2789:9\r\n #3 0x50928d in cfrReadFont afdko/c/tx/source/tx.c:137:9\r\n #4 0x508cc3 in doFile afdko/c/tx/source/tx.c:429:17\r\n #5 0x506b2e in doSingleFileSet afdko/c/tx/source/tx.c:488:5\r\n #6 0x4fc91e in parseArgs afdko/c/tx/source/tx.c:558:17\r\n #7 0x4f9470 in main afdko/c/tx/source/tx.c:1631:9\r\n #8 0x7f7bf34352b0 in __libc_start_main\r\n #9 0x41e5b9 in _start\r\n\r\n0x62a00000b228 is located 40 bytes to the right of 20480-byte region [0x62a000006200,0x62a00000b200)\r\nallocated by thread T0 here:\r\n #0 0x4c63f3 in __interceptor_malloc\r\n #1 0x6c9ac2 in mem_manage afdko/c/public/lib/source/tx_shared/tx_shared.c:73:20\r\n #2 0x5474a4 in dna_manage afdko/c/public/lib/source/cffread/cffread.c:271:17\r\n #3 0x7de64e in dnaGrow afdko/c/public/lib/source/dynarr/dynarr.c:86:23\r\n #4 0x7dec75 in dnaSetCnt afdko/c/public/lib/source/dynarr/dynarr.c:119:13\r\n #5 0x53e6fa in readCharStringsINDEX afdko/c/public/lib/source/cffread/cffread.c:1791:5\r\n #6 0x5295be in cfrBegFont afdko/c/public/lib/source/cffread/cffread.c:2769:9\r\n #7 0x50928d in cfrReadFont afdko/c/tx/source/tx.c:137:9\r\n #8 0x508cc3 in doFile afdko/c/tx/source/tx.c:429:17\r\n #9 0x506b2e in doSingleFileSet afdko/c/tx/source/tx.c:488:5\r\n #10 0x4fc91e in parseArgs afdko/c/tx/source/tx.c:558:17\r\n #11 0x4f9470 in main afdko/c/tx/source/tx.c:1631:9\r\n #12 0x7f7bf34352b0 in __libc_start_main\r\n\r\nSUMMARY: AddressSanitizer: heap-buffer-overflow afdko/c/public/lib/source/cffread/cffread.c:1843:19 in addID\r\nShadow bytes around the buggy address:\r\n 0x0c547fff95f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\r\n 0x0c547fff9600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\r\n 0x0c547fff9610: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\r\n 0x0c547fff9620: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\r\n 0x0c547fff9630: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\r\n=>0x0c547fff9640: fa fa fa fa fa[fa]fa fa fa fa fa fa fa fa fa fa\r\n 0x0c547fff9650: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\r\n 0x0c547fff9660: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\r\n 0x0c547fff9670: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\r\n 0x0c547fff9680: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\r\n 0x0c547fff9690: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\r\nShadow byte legend (one shadow byte represents 8 application bytes):\r\n Addressable: 00\r\n Partially addressable: 01 02 03 04 05 06 07\r\n Heap left redzone: fa\r\n Freed heap region: fd\r\n Stack left redzone: f1\r\n Stack mid redzone: f2\r\n Stack right redzone: f3\r\n Stack after return: f5\r\n Stack use after scope: f8\r\n Global redzone: f9\r\n Global init order: f6\r\n Poisoned by user: f7\r\n Container overflow: fc\r\n Array cookie: ac\r\n Intra object redzone: bb\r\n ASan internal: fe\r\n Left alloca redzone: ca\r\n Right alloca redzone: cb\r\n Shadow gap: cc\r\n==236657==ABORTING\r\n--- cut ---\r\n\r\nA non-instrumented version of \"tx\" crashes with a SIGSEGV when it reaches an unmapped memory area:\r\n\r\n--- cut ---\r\nProgram received signal SIGSEGV, Segmentation fault.\r\n0x0000000000417d1e in addID (h=0x7103a0, gid=2293, id=18997) at ../../../../../source/cffread/cffread.c:1843\r\n1843 info->cid = id;\r\n(gdb) print info\r\n$1 = (abfGlyphInfo *) 0x743000\r\n(gdb) print &h->glyphs.array[gid]\r\n$2 = (abfGlyphInfo *) 0x743000\r\n(gdb) print gid\r\n$3 = 2293\r\n(gdb) x/10gx 0x743000\r\n0x743000: Cannot access memory at address 0x743000\r\n(gdb) bt\r\n#0 0x0000000000417d1e in addID (h=0x7103a0, gid=2293, id=18997) at ../../../../../source/cffread/cffread.c:1843\r\n#1 0x0000000000412a57 in readCharset (h=0x7103a0) at ../../../../../source/cffread/cffread.c:2187\r\n#2 0x000000000040dd64 in cfrBegFont (h=0x7103a0, flags=4, origin=0, ttcIndex=0, top=0x6f6048, UDV=0x0) at ../../../../../source/cffread/cffread.c:2789\r\n#3 0x0000000000405e4e in cfrReadFont (h=0x6f6010, origin=0, ttcIndex=0) at ../../../../source/tx.c:137\r\n#4 0x0000000000405c9e in doFile (h=0x6f6010, srcname=0x7fffffffdf4c \"poc.otf\") at ../../../../source/tx.c:429\r\n#5 0x000000000040532e in doSingleFileSet (h=0x6f6010, srcname=0x7fffffffdf4c \"poc.otf\")\r\n at ../../../../source/tx.c:488\r\n#6 0x0000000000402f59 in parseArgs (h=0x6f6010, argc=2, argv=0x7fffffffdc50) at ../../../../source/tx.c:558\r\n#7 0x0000000000401df2 in main (argc=2, argv=0x7fffffffdc50) at ../../../../source/tx.c:1631\r\n(gdb)\r\n--- cut ---\r\n\r\nA similar Microsoft Edge renderer process crash is also shown below:\r\n\r\n--- cut ---\r\n(4d58.50bc): Access violation - code c0000005 (first chance)\r\nFirst chance exceptions are reported before any exception handling.\r\nThis exception may be expected and handled.\r\nDWrite!addID+0x33:\r\n00007ffb`29e6864b 66895cfe28 mov word ptr [rsi+rdi*8+28h],bx ds:000001ea`f5fee000=????\r\n\r\n0:038> ? rsi\r\nEvaluate expression: 2108661076032 = 000001ea`f5fe9040\r\n0:038> ? rdi\r\nEvaluate expression: 2547 = 00000000`000009f3\r\n0:038> db rsi+rdi*8+28\r\n000001ea`f5fee000 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee010 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee020 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee030 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee040 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee050 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee060 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n000001ea`f5fee070 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ?? ????????????????\r\n\r\n0:038> k\r\n # Child-SP RetAddr Call Site\r\n00 00000047`0fcfae10 00007ffb`29e6a262 DWrite!addID+0x33\r\n01 00000047`0fcfae40 00007ffb`29e6de84 DWrite!readCharset+0x10a\r\n02 00000047`0fcfae70 00007ffb`29e621e7 DWrite!cfrBegFont+0x5d8\r\n03 00000047`0fcfb700 00007ffb`29df157a DWrite!AdobeCFF2Snapshot+0x10f\r\n04 00000047`0fcfbc00 00007ffb`29df0729 DWrite!FontInstancer::InstanceCffTable+0x212\r\n05 00000047`0fcfbde0 00007ffb`29df039a DWrite!FontInstancer::CreateInstanceInternal+0x249\r\n06 00000047`0fcfc000 00007ffb`29dd5a4e DWrite!FontInstancer::CreateInstance+0x192\r\n07 00000047`0fcfc360 00007ffb`34eb61ab DWrite!DWriteFontFace::CreateInstancedStream+0x9e\r\n08 00000047`0fcfc3f0 00007ffb`34ea9148 d2d1!dxc::TextConvertor::InstanceFontResources+0x19f\r\n09 00000047`0fcfc510 00007ffb`0fb750f4 d2d1!dxc::CXpsPrintControl::Close+0xc8\r\n0a 00000047`0fcfc560 00007ffb`0fb4fcb0 edgehtml!CDXPrintControl::Close+0x44\r\n0b 00000047`0fcfc5b0 00007ffb`0fb547ad edgehtml!CTemplatePrinter::EndPrintD2D+0x5c\r\n0c 00000047`0fcfc5e0 00007ffb`0fa2b515 edgehtml!CPrintManagerTemplatePrinter::endPrint+0x2d\r\n0d 00000047`0fcfc610 00007ffb`0f689175 edgehtml!CFastDOM::CMSPrintManagerTemplatePrinter::Trampoline_endPrint+0x45\r\n0e 00000047`0fcfc650 00007ffb`0eb568f1 edgehtml!CFastDOM::CMSPrintManagerTemplatePrinter::Profiler_endPrint+0x25\r\n[...]\r\n--- cut ---\r\n\r\n-----=====[ References ]=====-----\r\n\r\n[1] https://blog.typekit.com/2014/09/19/new-from-adobe-type-open-sourced-font-development-tools/\r\n[2] https://github.com/adobe-type-tools/afdko\r\n[3] https://docs.microsoft.com/en-us/windows/desktop/directwrite/direct-write-portal\r\n[4] https://medium.com/variable-fonts/https-medium-com-tiro-introducing-opentype-variable-fonts-12ba6cd2369\r\n\r\n\r\nProof of Concept:\r\nhttps://github.com/offensive-security/exploitdb-bin-sploits/raw/master/bin-sploits/47095.zip", "cvss": {"score": 0.0, "vector": "NONE"}, "sourceHref": "https://www.exploit-db.com/download/47095"}], "kaspersky": [{"lastseen": "2020-09-02T11:46:30", "bulletinFamily": "info", "cvelist": ["CVE-2019-1123", "CVE-2019-1090", "CVE-2019-1126", "CVE-2019-1082", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1086", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-0811", "CVE-2019-1095", "CVE-2019-0999", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-0785", "CVE-2019-1071", "CVE-2019-1130", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-0975"], "description": "### *Detect date*:\n07/09/2019\n\n### *Severity*:\nCritical\n\n### *Description*:\nMultiple vulnerabilities were found in Microsoft Windows. Malicious users can exploit these vulnerabilities to execute arbitrary code, gain privileges, obtain sensitive information, 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 Server 2019 \nWindows Server 2012 R2 \nWindows Server 2012 (Server Core installation) \nWindows Server 2012 R2 (Server Core installation) \nWindows Server 2016 \nWindows Server 2012 \nWindows Server, version 1903 (Server Core installation) \nWindows 7 for 32-bit Systems Service Pack 1 \nWindows Server 2008 R2 for x64-based Systems Service Pack 1 \nWindows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) \nWindows Server 2008 for 32-bit Systems Service Pack 2 \nWindows 7 for x64-based Systems Service Pack 1 \nWindows Server 2008 for x64-based Systems Service Pack 2 \nWindows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) \nWindows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) \nWindows Server 2008 R2 for Itanium-Based Systems Service Pack 1 \nWindows Server 2008 for Itanium-Based Systems Service Pack 2 \nWindows 10 Version 1803 for ARM64-based Systems \nWindows 10 Version 1803 for 32-bit Systems \nWindows 10 Version 1903 for ARM64-based Systems \nWindows 10 Version 1903 for x64-based Systems \nWindows 10 Version 1803 for x64-based Systems \nWindows 10 Version 1809 for 32-bit Systems \nWindows 10 Version 1709 for 32-bit Systems \nWindows 10 Version 1809 for x64-based Systems \nWindows 10 Version 1709 for ARM64-based Systems \nWindows 10 Version 1809 for ARM64-based Systems \nWindows 10 Version 1903 for 32-bit Systems \nWindows 10 for 32-bit Systems \nWindows 10 for x64-based Systems \nWindows 10 Version 1607 for 32-bit Systems \nWindows 10 Version 1703 for 32-bit Systems \nWindows 10 Version 1703 for x64-based Systems \nWindows RT 8.1 \nWindows 8.1 for x64-based systems \nWindows 10 Version 1607 for x64-based Systems \nWindows 8.1 for 32-bit systems \nMicrosoft .NET Framework 2.0 Service Pack 2 \nMicrosoft .NET Framework 4.5.2 \nWindows Server 2019 (Server Core installation) \nWindows Server, version 1803 (Server Core Installation) \nMicrosoft.IdentityModel 7.0.0 \nMicrosoft .NET Framework 3.5 AND 4.8 \nMicrosoft SharePoint Foundation 2013 Service Pack 1 \nMicrosoft SharePoint Foundation 2010 Service Pack 2 \nMicrosoft .NET Framework 3.5.1 \nMicrosoft .NET Framework 4.8 \nMicrosoft Remote Desktop for Android \nMicrosoft .NET Framework 3.0 Service Pack 2 \nMicrosoft .NET Framework 3.5 \nMicrosoft SharePoint Enterprise Server 2016 \nMicrosoft .NET Framework 4.6 \nWindows Server 2016 (Server Core installation) \nMicrosoft SharePoint Enterprise Server 2013 Service Pack 1 \nMicrosoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 \nMicrosoft Remote Desktop for IoS \nMicrosoft .NET Framework 3.5 AND 4.7.2 \nWindows 10 Version 1709 for x64-based Systems \nMicrosoft SharePoint Server 2019 \nMicrosoft .NET Framework 4.6/4.6.1/4.6.2\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-2019-1120](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1120>) \n[CVE-2019-1121](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1121>) \n[CVE-2019-1086](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1086>) \n[CVE-2019-1096](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1096>) \n[CVE-2019-1089](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1089>) \n[CVE-2019-1130](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1130>) \n[CVE-2019-1087](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1087>) \n[CVE-2019-1037](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1037>) \n[CVE-2019-1090](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1090>) \n[CVE-2019-0880](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0880>) \n[CVE-2019-1085](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1085>) \n[CVE-2019-1006](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1006>) \n[CVE-2019-0785](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0785>) \n[CVE-2019-1108](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1108>) \n[CVE-2019-0865](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0865>) \n[CVE-2019-1095](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1095>) \n[CVE-2019-1129](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1129>) \n[CVE-2019-1082](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1082>) \n[CVE-2019-0999](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0999>) \n[CVE-2019-1126](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1126>) \n[CVE-2019-1071](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1071>) \n[CVE-2019-1094](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1094>) \n[CVE-2019-1122](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1122>) \n[CVE-2019-1091](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1091>) \n[CVE-2019-1117](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1117>) \n[CVE-2019-0966](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0966>) \n[CVE-2019-1074](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1074>) \n[CVE-2019-1127](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1127>) \n[CVE-2019-1102](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1102>) \n[CVE-2019-1119](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1119>) \n[CVE-2019-0975](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0975>) \n[CVE-2019-1093](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1093>) \n[CVE-2019-1124](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1124>) \n[CVE-2019-1128](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1128>) \n[CVE-2019-1123](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1123>) \n[CVE-2019-1073](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1073>) \n[CVE-2019-0887](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0887>) \n[CVE-2019-1097](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1097>) \n[CVE-2019-0811](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-0811>) \n[CVE-2019-1088](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1088>) \n[CVE-2019-1067](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1067>) \n[CVE-2019-1118](<https://portal.msrc.microsoft.com/api/security-guidance/en-US/CVE/CVE-2019-1118>) \n\n\n### *Impacts*:\nACE \n\n### *Related products*:\n[Microsoft Windows Server 2012](<https://threats.kaspersky.com/en/product/Microsoft-Windows-Server-2012/>)\n\n### *CVE-IDS*:\n[CVE-2019-0785](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0785>)0.0Unknown \n[CVE-2019-1120](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1120>)0.0Unknown \n[CVE-2019-1130](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1130>)0.0Unknown \n[CVE-2019-1127](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1127>)0.0Unknown \n[CVE-2019-1086](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1086>)0.0Unknown \n[CVE-2019-1128](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1128>)0.0Unknown \n[CVE-2019-0999](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0999>)0.0Unknown \n[CVE-2019-1129](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1129>)0.0Unknown \n[CVE-2019-1093](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1093>)0.0Unknown \n[CVE-2019-1108](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1108>)0.0Unknown \n[CVE-2019-1097](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1097>)0.0Unknown \n[CVE-2019-1087](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1087>)0.0Unknown \n[CVE-2019-1123](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1123>)0.0Unknown \n[CVE-2019-1089](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1089>)0.0Unknown \n[CVE-2019-1095](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1095>)0.0Unknown \n[CVE-2019-1124](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1124>)0.0Unknown \n[CVE-2019-1091](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1091>)0.0Unknown \n[CVE-2019-1096](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1096>)0.0Unknown \n[CVE-2019-0880](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0880>)0.0Unknown \n[CVE-2019-1006](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1006>)0.0Unknown \n[CVE-2019-1117](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1117>)0.0Unknown \n[CVE-2019-1088](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1088>)0.0Unknown \n[CVE-2019-1071](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1071>)0.0Unknown \n[CVE-2019-1121](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1121>)0.0Unknown \n[CVE-2019-1094](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1094>)0.0Unknown \n[CVE-2019-1119](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1119>)0.0Unknown \n[CVE-2019-1122](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1122>)0.0Unknown \n[CVE-2019-0865](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0865>)0.0Unknown \n[CVE-2019-1037](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1037>)0.0Unknown \n[CVE-2019-0966](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0966>)0.0Unknown \n[CVE-2019-1102](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1102>)0.0Unknown \n[CVE-2019-1118](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1118>)0.0Unknown \n[CVE-2019-1085](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1085>)0.0Unknown \n[CVE-2019-0811](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0811>)0.0Unknown \n[CVE-2019-0887](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0887>)0.0Unknown \n[CVE-2019-1090](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1090>)0.0Unknown \n[CVE-2019-1074](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1074>)0.0Unknown \n[CVE-2019-1073](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1073>)0.0Unknown \n[CVE-2019-1126](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1126>)0.0Unknown \n[CVE-2019-1082](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1082>)0.0Unknown \n[CVE-2019-0975](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0975>)0.0Unknown \n[CVE-2019-1067](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1067>)0.0Unknown\n\n### *Microsoft official advisories*:\n\n\n### *KB list*:\n[4507464](<http://support.microsoft.com/kb/4507464>) \n[4507460](<http://support.microsoft.com/kb/4507460>) \n[4507457](<http://support.microsoft.com/kb/4507457>) \n[4507448](<http://support.microsoft.com/kb/4507448>) \n[4507453](<http://support.microsoft.com/kb/4507453>) \n[4507469](<http://support.microsoft.com/kb/4507469>) \n[4507435](<http://support.microsoft.com/kb/4507435>) \n[4507462](<http://support.microsoft.com/kb/4507462>) \n[4507455](<http://support.microsoft.com/kb/4507455>) \n[4507458](<http://support.microsoft.com/kb/4507458>) \n[4507450](<http://support.microsoft.com/kb/4507450>)", "edition": 1, "modified": "2020-07-22T00:00:00", "published": "2019-07-09T00:00:00", "id": "KLA11511", "href": "https://threats.kaspersky.com/en/vulnerability/KLA11511", "title": "\r KLA11511Multiple vulnerabilities in Microsoft Windows ", "type": "kaspersky", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "nessus": [{"lastseen": "2021-02-06T14:31:53", "description": "The remote Windows host is missing security update 4507455.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n DirectX improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-0999)\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)", "edition": 11, "cvss3": {"score": 8.8, "vector": "AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2019-07-09T00:00:00", "title": "KB4507455: Windows 10 Version 1709 July 2019 Security Update (SWAPGS)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-1095", "CVE-2019-0999", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "modified": "2019-07-09T00:00:00", "cpe": ["cpe:/o:microsoft:windows", "cpe:/a:microsoft:edge"], "id": "SMB_NT_MS19_JUL_4507455.NASL", "href": "https://www.tenable.com/plugins/nessus/126575", "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(126575);\n script_version(\"1.10\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2021/02/05\");\n\n script_cve_id(\n \"CVE-2019-0865\",\n \"CVE-2019-0880\",\n \"CVE-2019-0887\",\n \"CVE-2019-0966\",\n \"CVE-2019-0999\",\n \"CVE-2019-1001\",\n \"CVE-2019-1004\",\n \"CVE-2019-1006\",\n \"CVE-2019-1037\",\n \"CVE-2019-1056\",\n \"CVE-2019-1059\",\n \"CVE-2019-1062\",\n \"CVE-2019-1063\",\n \"CVE-2019-1067\",\n \"CVE-2019-1071\",\n \"CVE-2019-1073\",\n \"CVE-2019-1074\",\n \"CVE-2019-1083\",\n \"CVE-2019-1085\",\n \"CVE-2019-1086\",\n \"CVE-2019-1087\",\n \"CVE-2019-1088\",\n \"CVE-2019-1089\",\n \"CVE-2019-1091\",\n \"CVE-2019-1092\",\n \"CVE-2019-1093\",\n \"CVE-2019-1094\",\n \"CVE-2019-1095\",\n \"CVE-2019-1096\",\n \"CVE-2019-1097\",\n \"CVE-2019-1102\",\n \"CVE-2019-1103\",\n \"CVE-2019-1104\",\n \"CVE-2019-1106\",\n \"CVE-2019-1107\",\n \"CVE-2019-1108\",\n \"CVE-2019-1113\",\n \"CVE-2019-1117\",\n \"CVE-2019-1118\",\n \"CVE-2019-1119\",\n \"CVE-2019-1120\",\n \"CVE-2019-1121\",\n \"CVE-2019-1122\",\n \"CVE-2019-1123\",\n \"CVE-2019-1124\",\n \"CVE-2019-1125\",\n \"CVE-2019-1127\",\n \"CVE-2019-1128\",\n \"CVE-2019-1129\",\n \"CVE-2019-1130\"\n );\n script_xref(name:\"MSKB\", value:\"4507455\");\n script_xref(name:\"MSFT\", value:\"MS19-4507455\");\n\n script_name(english:\"KB4507455: Windows 10 Version 1709 July 2019 Security Update (SWAPGS)\");\n script_summary(english:\"Checks for rollup.\");\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 4507455.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n DirectX improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-0999)\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)\");\n # https://support.microsoft.com/en-us/help/4507455/windows-10-update-kb4507455\n script_set_attribute(attribute:\"see_also\", value:\"http://www.nessus.org/u?4741f3da\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4507455.\");\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:N/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-2019-1128\");\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:\"2019/07/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2019/07/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2019/07/09\");\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:\"cpe\", value:\"cpe:/a:microsoft:edge\");\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) 2019-2021 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 = \"MS19-07\";\nkbs = make_list('4507455');\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);\nmy_os_build = get_kb_item(\"SMB/WindowsVersionBuild\");\nproductname = get_kb_item_or_exit(\"SMB/ProductName\");\n\nif (my_os_build == \"16299\" && \"enterprise\" >!< tolower(productname) && \"education\" >!< tolower(productname) && \"server\" >!< tolower(productname))\n audit(AUDIT_OS_NOT, \"a supported version of Windows\");\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:\"16299\",\n rollup_date:\"07_2019\",\n bulletin:bulletin,\n rollup_kb_list:[4507455])\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": "2021-02-06T14:31:52", "description": "The remote Windows host is missing security update 4507453.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)", "edition": 13, "cvss3": {"score": 8.8, "vector": "AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2019-07-09T00:00:00", "title": "KB4507453: Windows 10 Version 1903 July 2019 Security Update (SWAPGS)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-1090", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-1095", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "modified": "2019-07-09T00:00:00", "cpe": ["cpe:/o:microsoft:windows", "cpe:/a:microsoft:edge"], "id": "SMB_NT_MS19_JUL_4507453.NASL", "href": "https://www.tenable.com/plugins/nessus/126574", "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(126574);\n script_version(\"1.9\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2021/02/05\");\n\n script_cve_id(\n \"CVE-2019-0865\",\n \"CVE-2019-0880\",\n \"CVE-2019-0887\",\n \"CVE-2019-0966\",\n \"CVE-2019-1001\",\n \"CVE-2019-1004\",\n \"CVE-2019-1006\",\n \"CVE-2019-1037\",\n \"CVE-2019-1056\",\n \"CVE-2019-1059\",\n \"CVE-2019-1062\",\n \"CVE-2019-1063\",\n \"CVE-2019-1067\",\n \"CVE-2019-1071\",\n \"CVE-2019-1073\",\n \"CVE-2019-1074\",\n \"CVE-2019-1083\",\n \"CVE-2019-1085\",\n \"CVE-2019-1086\",\n \"CVE-2019-1087\",\n \"CVE-2019-1088\",\n \"CVE-2019-1089\",\n \"CVE-2019-1090\",\n \"CVE-2019-1091\",\n \"CVE-2019-1092\",\n \"CVE-2019-1093\",\n \"CVE-2019-1094\",\n \"CVE-2019-1095\",\n \"CVE-2019-1096\",\n \"CVE-2019-1097\",\n \"CVE-2019-1102\",\n \"CVE-2019-1103\",\n \"CVE-2019-1104\",\n \"CVE-2019-1106\",\n \"CVE-2019-1107\",\n \"CVE-2019-1108\",\n \"CVE-2019-1113\",\n \"CVE-2019-1117\",\n \"CVE-2019-1118\",\n \"CVE-2019-1119\",\n \"CVE-2019-1120\",\n \"CVE-2019-1121\",\n \"CVE-2019-1122\",\n \"CVE-2019-1123\",\n \"CVE-2019-1124\",\n \"CVE-2019-1125\",\n \"CVE-2019-1127\",\n \"CVE-2019-1128\",\n \"CVE-2019-1129\",\n \"CVE-2019-1130\"\n );\n script_xref(name:\"MSKB\", value:\"4507453\");\n script_xref(name:\"MSFT\", value:\"MS19-4507453\");\n\n script_name(english:\"KB4507453: Windows 10 Version 1903 July 2019 Security Update (SWAPGS)\");\n script_summary(english:\"Checks for rollup.\");\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 4507453.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)\");\n # https://support.microsoft.com/en-us/help/4507453/windows-10-update-kb4507453\n script_set_attribute(attribute:\"see_also\", value:\"http://www.nessus.org/u?29fe0038\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4507453.\");\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:N/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-2019-1128\");\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:\"2019/07/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2019/07/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2019/07/09\");\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:\"cpe\", value:\"cpe:/a:microsoft:edge\");\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) 2019-2021 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 = \"MS19-07\";\nkbs = make_list('4507453');\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:\"18362\",\n rollup_date:\"07_2019\",\n bulletin:bulletin,\n rollup_kb_list:[4507453])\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": "2021-02-06T14:31:57", "description": "The remote Windows host is missing security update 4507469.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A security feature bypass vulnerability exists in Active\n Directory Federation Services (ADFS) which could allow\n an attacker to bypass the extranet lockout policy.\n (CVE-2019-1126)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - A memory corruption vulnerability exists in the Windows\n Server DHCP service when an attacker sends specially\n crafted packets to a DHCP failover server. An attacker\n who successfully exploited the vulnerability could\n either run arbitrary code on the DHCP failover server or\n cause the DHCP service to become nonresponsive.\n (CVE-2019-0785)\n\n - A security feature bypass vulnerability exists when\n Active Directory Federation Services (ADFS) improperly\n updates its list of banned IP addresses.\n (CVE-2019-0975)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A denial of service vulnerability exists in Windows DNS\n Server when it fails to properly handle DNS queries. An\n attacker who successfully exploited this vulnerability\n could cause the DNS Server service to become\n nonresponsive. (CVE-2019-0811)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)", "edition": 13, "cvss3": {"score": 8.8, "vector": "AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2019-07-09T00:00:00", "title": "KB4507469: Windows 10 Version 1809 and Windows Server 2019 July 2019 Security Update (SWAPGS)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-1090", "CVE-2019-1126", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-0811", "CVE-2019-1095", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-0785", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-0975", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "modified": "2019-07-09T00:00:00", "cpe": ["cpe:/o:microsoft:windows", "cpe:/a:microsoft:edge"], "id": "SMB_NT_MS19_JUL_4507469.NASL", "href": "https://www.tenable.com/plugins/nessus/126579", "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(126579);\n script_version(\"1.9\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2021/02/05\");\n\n script_cve_id(\n \"CVE-2019-0785\",\n \"CVE-2019-0811\",\n \"CVE-2019-0865\",\n \"CVE-2019-0880\",\n \"CVE-2019-0887\",\n \"CVE-2019-0966\",\n \"CVE-2019-0975\",\n \"CVE-2019-1001\",\n \"CVE-2019-1004\",\n \"CVE-2019-1006\",\n \"CVE-2019-1037\",\n \"CVE-2019-1056\",\n \"CVE-2019-1059\",\n \"CVE-2019-1062\",\n \"CVE-2019-1063\",\n \"CVE-2019-1067\",\n \"CVE-2019-1071\",\n \"CVE-2019-1073\",\n \"CVE-2019-1074\",\n \"CVE-2019-1083\",\n \"CVE-2019-1085\",\n \"CVE-2019-1086\",\n \"CVE-2019-1087\",\n \"CVE-2019-1088\",\n \"CVE-2019-1089\",\n \"CVE-2019-1090\",\n \"CVE-2019-1091\",\n \"CVE-2019-1092\",\n \"CVE-2019-1093\",\n \"CVE-2019-1094\",\n \"CVE-2019-1095\",\n \"CVE-2019-1096\",\n \"CVE-2019-1097\",\n \"CVE-2019-1102\",\n \"CVE-2019-1103\",\n \"CVE-2019-1104\",\n \"CVE-2019-1106\",\n \"CVE-2019-1107\",\n \"CVE-2019-1108\",\n \"CVE-2019-1113\",\n \"CVE-2019-1117\",\n \"CVE-2019-1118\",\n \"CVE-2019-1119\",\n \"CVE-2019-1120\",\n \"CVE-2019-1121\",\n \"CVE-2019-1122\",\n \"CVE-2019-1123\",\n \"CVE-2019-1124\",\n \"CVE-2019-1125\",\n \"CVE-2019-1126\",\n \"CVE-2019-1127\",\n \"CVE-2019-1128\",\n \"CVE-2019-1129\",\n \"CVE-2019-1130\"\n );\n script_xref(name:\"MSKB\", value:\"4507469\");\n script_xref(name:\"MSFT\", value:\"MS19-4507469\");\n\n script_name(english:\"KB4507469: Windows 10 Version 1809 and Windows Server 2019 July 2019 Security Update (SWAPGS)\");\n script_summary(english:\"Checks for rollup.\");\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 4507469.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A security feature bypass vulnerability exists in Active\n Directory Federation Services (ADFS) which could allow\n an attacker to bypass the extranet lockout policy.\n (CVE-2019-1126)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - A memory corruption vulnerability exists in the Windows\n Server DHCP service when an attacker sends specially\n crafted packets to a DHCP failover server. An attacker\n who successfully exploited the vulnerability could\n either run arbitrary code on the DHCP failover server or\n cause the DHCP service to become nonresponsive.\n (CVE-2019-0785)\n\n - A security feature bypass vulnerability exists when\n Active Directory Federation Services (ADFS) improperly\n updates its list of banned IP addresses.\n (CVE-2019-0975)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A denial of service vulnerability exists in Windows DNS\n Server when it fails to properly handle DNS queries. An\n attacker who successfully exploited this vulnerability\n could cause the DNS Server service to become\n nonresponsive. (CVE-2019-0811)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)\");\n # https://support.microsoft.com/en-us/help/4507469/windows-10-update-kb4507469\n script_set_attribute(attribute:\"see_also\", value:\"http://www.nessus.org/u?e5ce6fe4\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4507469.\");\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:N/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-2019-1128\");\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:\"2019/07/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2019/07/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2019/07/09\");\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:\"cpe\", value:\"cpe:/a:microsoft:edge\");\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) 2019-2021 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 = \"MS19-07\";\nkbs = make_list('4507469');\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:\"07_2019\",\n bulletin:bulletin,\n rollup_kb_list:[4507469])\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": "2021-02-06T14:31:50", "description": "The remote Windows host is missing security update 4507435.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n DirectX improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-0999)\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)", "edition": 13, "cvss3": {"score": 8.8, "vector": "AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}, "published": "2019-07-09T00:00:00", "title": "KB4507435: Windows 10 Version 1803 July 2019 Security Update (SWAPGS)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-1090", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-1095", "CVE-2019-0999", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "modified": "2019-07-09T00:00:00", "cpe": ["cpe:/o:microsoft:windows", "cpe:/a:microsoft:edge"], "id": "SMB_NT_MS19_JUL_4507435.NASL", "href": "https://www.tenable.com/plugins/nessus/126569", "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(126569);\n script_version(\"1.9\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2021/02/05\");\n\n script_cve_id(\n \"CVE-2019-0865\",\n \"CVE-2019-0880\",\n \"CVE-2019-0887\",\n \"CVE-2019-0966\",\n \"CVE-2019-0999\",\n \"CVE-2019-1001\",\n \"CVE-2019-1004\",\n \"CVE-2019-1006\",\n \"CVE-2019-1037\",\n \"CVE-2019-1056\",\n \"CVE-2019-1059\",\n \"CVE-2019-1062\",\n \"CVE-2019-1063\",\n \"CVE-2019-1067\",\n \"CVE-2019-1071\",\n \"CVE-2019-1073\",\n \"CVE-2019-1074\",\n \"CVE-2019-1083\",\n \"CVE-2019-1085\",\n \"CVE-2019-1086\",\n \"CVE-2019-1087\",\n \"CVE-2019-1088\",\n \"CVE-2019-1089\",\n \"CVE-2019-1090\",\n \"CVE-2019-1091\",\n \"CVE-2019-1092\",\n \"CVE-2019-1093\",\n \"CVE-2019-1094\",\n \"CVE-2019-1095\",\n \"CVE-2019-1096\",\n \"CVE-2019-1097\",\n \"CVE-2019-1102\",\n \"CVE-2019-1103\",\n \"CVE-2019-1104\",\n \"CVE-2019-1106\",\n \"CVE-2019-1107\",\n \"CVE-2019-1108\",\n \"CVE-2019-1113\",\n \"CVE-2019-1117\",\n \"CVE-2019-1118\",\n \"CVE-2019-1119\",\n \"CVE-2019-1120\",\n \"CVE-2019-1121\",\n \"CVE-2019-1122\",\n \"CVE-2019-1123\",\n \"CVE-2019-1124\",\n \"CVE-2019-1125\",\n \"CVE-2019-1127\",\n \"CVE-2019-1128\",\n \"CVE-2019-1129\",\n \"CVE-2019-1130\"\n );\n script_xref(name:\"MSKB\", value:\"4507435\");\n script_xref(name:\"MSFT\", value:\"MS19-4507435\");\n\n script_name(english:\"KB4507435: Windows 10 Version 1803 July 2019 Security Update (SWAPGS)\");\n script_summary(english:\"Checks for rollup.\");\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 4507435.\nIt is, therefore, affected by multiple vulnerabilities :\n\n - An elevation of privilege vulnerability exists when\n DirectX improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-0999)\n\n - A remote code execution vulnerability exists in .NET\n software when the software fails to check the source\n markup of a file. An attacker who successfully exploited\n the vulnerability could run arbitrary code in the\n context of the current user. If the current user is\n logged on with administrative user rights, an attacker\n could take control of the affected system. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with full user rights.\n (CVE-2019-1113)\n\n - A local elevation of privilege vulnerability exists in\n how splwow64.exe handles certain calls. An attacker who\n successfully exploited the vulnerability could elevate\n privileges on an affected system from low-integrity to\n medium-integrity. This vulnerability by itself does not\n allow arbitrary code execution; however, it could allow\n arbitrary code to be run if the attacker uses it in\n combination with another vulnerability (such as a remote\n code execution vulnerability or another elevation of\n privilege vulnerability) that is capable of leveraging\n the elevated privileges when code execution is\n attempted. (CVE-2019-0880)\n\n - A denial of service vulnerability exists when Microsoft\n Hyper-V on a host server fails to properly validate\n input from a privileged user on a guest operating\n system. (CVE-2019-0966)\n\n - A remote code execution vulnerability exists in the way\n that the Chakra scripting engine handles objects in\n memory in Microsoft Edge. The vulnerability could\n corrupt memory in such a way that an attacker could\n execute arbitrary code in the context of the current\n user. An attacker who successfully exploited the\n vulnerability could gain the same user rights as the\n current user. (CVE-2019-1062, CVE-2019-1092,\n CVE-2019-1103, CVE-2019-1106, CVE-2019-1107)\n\n - An information disclosure vulnerability exists when the\n Windows RDP client improperly discloses the contents of\n its memory. An attacker who successfully exploited this\n vulnerability could obtain information to further\n compromise the users system. (CVE-2019-1108)\n\n - An information disclosure vulnerability exists when the\n win32k component improperly provides kernel information.\n An attacker who successfully exploited the vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1096)\n\n - An elevation of privilege vulnerability exists in the\n way Windows Error Reporting (WER) handles files. An\n attacker who successfully exploited this vulnerability\n could run arbitrary code in kernel mode. An attacker\n could then install programs; view, change, or delete\n data; or create new accounts with administrator\n privileges. (CVE-2019-1037)\n\n - A remote code execution vulnerability exists in the way\n the scripting engine handles objects in memory in\n Microsoft browsers. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1001)\n\n - A remote code execution vulnerability exists when\n Internet Explorer improperly accesses objects in memory.\n The vulnerability could corrupt memory in such a way\n that an attacker could execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1063)\n\n - An elevation of privilege vulnerability exists in\n Microsoft Windows where certain folders, with local\n service privilege, are vulnerable to symbolic link\n attack. An attacker who successfully exploited this\n vulnerability could potentially access unauthorized\n information. The update addresses this vulnerability by\n not allowing symbolic links in these scenarios.\n (CVE-2019-1074)\n\n - An elevation of privilege vulnerability exists in the\n way that the dnsrslvr.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1090)\n\n - A remote code execution vulnerability exists in the way\n that Microsoft browsers access objects in memory. The\n vulnerability could corrupt memory in a way that could\n allow an attacker to execute arbitrary code in the\n context of the current user. An attacker who\n successfully exploited the vulnerability could gain the\n same user rights as the current user. (CVE-2019-1104)\n\n - An information disclosure vulnerability exists when\n DirectWrite improperly discloses the contents of its\n memory. An attacker who successfully exploited the\n vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how DirectWrite handles objects in memory.\n (CVE-2019-1093, CVE-2019-1097)\n\n - An information disclosure vulnerability exists when the\n Windows GDI component improperly discloses the contents\n of its memory. An attacker who successfully exploited\n the vulnerability could obtain information to further\n compromise the users system. There are multiple ways an\n attacker could exploit the vulnerability, such as by\n convincing a user to open a specially crafted document,\n or by convincing a user to visit an untrusted webpage.\n The security update addresses the vulnerability by\n correcting how the Windows GDI component handles objects\n in memory. (CVE-2019-1094, CVE-2019-1095)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. An authenticated attacker could exploit this\n vulnerability by running a specially crafted\n application. The update addresses the vulnerability by\n correcting how the Windows kernel handles objects in\n memory. (CVE-2019-1071)\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-2019-1067)\n\n - An elevation of privilege exists in Windows Audio\n Service. An attacker who successfully exploited the\n vulnerability could run arbitrary code with elevated\n privileges. (CVE-2019-1086, CVE-2019-1087,\n CVE-2019-1088)\n\n - A remote code execution vulnerability exists in the way\n that the scripting engine handles objects in memory in\n Internet Explorer. The vulnerability could corrupt\n memory in such a way that an attacker could execute\n arbitrary code in the context of the current user. An\n attacker who successfully exploited the vulnerability\n could gain the same user rights as the current user.\n (CVE-2019-1004, CVE-2019-1056, CVE-2019-1059)\n\n - A remote code execution vulnerability exists in Remote\n Desktop Services formerly known as Terminal Services\n when an authenticated attacker abuses clipboard\n redirection. An attacker who successfully exploited this\n vulnerability could execute arbitrary code on the victim\n system. An attacker could then install programs; view,\n change, or delete data; or create new accounts with full\n user rights. (CVE-2019-0887)\n\n - An elevation of privilege vulnerability exists in the\n way that the wlansvc.dll handles objects in memory. An\n attacker who successfully exploited the vulnerability\n could execute code with elevated permissions.\n (CVE-2019-1085)\n\n - A denial of service vulnerability exists when Microsoft\n Common Object Runtime Library improperly handles web\n requests. An attacker who successfully exploited this\n vulnerability could cause a denial of service against a\n .NET web application. A remote unauthenticated attacker\n could exploit this vulnerability by issuing specially\n crafted requests to the .NET application. The update\n addresses the vulnerability by correcting how the .NET\n web application handles web requests. (CVE-2019-1083)\n\n - An elevation of privilege vulnerability exists in\n rpcss.dll when the RPC service Activation Kernel\n improperly handles an RPC request. (CVE-2019-1089)\n\n - An information disclosure vulnerability exists when the\n Windows kernel improperly handles objects in memory. An\n attacker who successfully exploited this vulnerability\n could obtain information to further compromise the users\n system. (CVE-2019-1073)\n\n - A denial of service vulnerability exists when SymCrypt\n improperly handles a specially crafted digital\n signature. An attacker could exploit the vulnerability\n by creating a specially crafted connection or message.\n The security update addresses the vulnerability by\n correcting the way SymCrypt handles digital signatures.\n (CVE-2019-0865)\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-2019-1102)\n\n - An authentication bypass vulnerability exists in Windows\n Communication Foundation (WCF) and Windows Identity\n Foundation (WIF), allowing signing of SAML tokens with\n arbitrary symmetric keys. This vulnerability allows an\n attacker to impersonate another user, which can lead to\n elevation of privileges. The vulnerability exists in\n WCF, WIF 3.5 and above in .NET Framework, WIF 1.0\n component in Windows, WIF Nuget package, and WIF\n implementation in SharePoint. An unauthenticated\n attacker can exploit this by signing a SAML token with\n any arbitrary symmetric key. This security update\n addresses the issue by ensuring all versions of WCF and\n WIF validate the key used to sign SAML tokens correctly.\n (CVE-2019-1006)\n\n - An elevation of privilege vulnerability exists when\n Windows AppX Deployment Service (AppXSVC) improperly\n handles hard links. An attacker who successfully\n exploited this vulnerability could run processes in an\n elevated context. An attacker could then install\n programs; view, change or delete data. (CVE-2019-1129,\n CVE-2019-1130)\n\n - An information disclosure vulnerability exists when\n Unistore.dll fails to properly handle objects in memory.\n An attacker who successfully exploited the vulnerability\n could potentially disclose memory contents of an\n elevated process. (CVE-2019-1091)\n\n - A remote code execution vulnerability exists in the way\n that DirectWrite handles objects in memory. An attacker\n who successfully exploited this vulnerability could take\n control of the affected system. An attacker could then\n 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 an untrusted webpage. The security update\n addresses the vulnerability by correcting how\n DirectWrite handles objects in memory. (CVE-2019-1117,\n CVE-2019-1118, CVE-2019-1119, CVE-2019-1120,\n CVE-2019-1121, CVE-2019-1122, CVE-2019-1123,\n CVE-2019-1124, CVE-2019-1127, CVE-2019-1128)\n \n - An information disclosure vulnerability exists when\n certain central processing units (CPU) speculatively\n access memory. An attacker who successfully exploited\n the vulnerability could read privileged data across\n trust boundaries. (CVE-2019-1125)\");\n # https://support.microsoft.com/en-us/help/4507435/windows-10-update-kb4507435\n script_set_attribute(attribute:\"see_also\", value:\"http://www.nessus.org/u?3bfac69e\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply Cumulative Update KB4507435.\");\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:N/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-2019-1128\");\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:\"2019/07/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2019/07/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2019/07/09\");\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:\"cpe\", value:\"cpe:/a:microsoft:edge\");\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) 2019-2021 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 = \"MS19-07\";\nkbs = make_list('4507435');\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:\"17134\",\n rollup_date:\"07_2019\",\n bulletin:bulletin,\n rollup_kb_list:[4507435])\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"}}], "openvas": [{"lastseen": "2020-07-21T20:40:44", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-0683", "CVE-2019-1090", "CVE-2019-1126", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-0998", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-0811", "CVE-2019-1095", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-0785", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-0975", "CVE-2019-1056", "CVE-2019-1092", "CVE-2019-1125"], "description": "This host is missing a critical security\n update according to Microsoft KB4507453", "modified": "2020-07-17T00:00:00", "published": "2019-07-10T00:00:00", "id": "OPENVAS:1361412562310815410", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310815410", "type": "openvas", "title": "Microsoft Windows Multiple Vulnerabilities (KB4507453)", "sourceData": "# Copyright (C) 2019 Greenbone Networks GmbH\n# Some text descriptions might be excerpted from (a) referenced\n# source(s), and are Copyright (C) by the respective right holder(s).\n#\n# SPDX-License-Identifier: GPL-2.0-or-later\n#\n# This program is free software; you can redistribute it and/or\n# modify it under the terms of the GNU General Public License\n# as published by the Free Software Foundation; either version 2\n# of the License, or (at your option) any later version.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.815410\");\n script_version(\"2020-07-17T05:57:41+0000\");\n script_cve_id(\"CVE-2019-0683\", \"CVE-2019-0785\", \"CVE-2019-0811\", \"CVE-2019-0865\",\n \"CVE-2019-0880\", \"CVE-2019-0887\", \"CVE-2019-0966\", \"CVE-2019-0975\",\n \"CVE-2019-0998\", \"CVE-2019-1001\", \"CVE-2019-1004\", \"CVE-2019-1006\",\n \"CVE-2019-1037\", \"CVE-2019-1056\", \"CVE-2019-1059\", \"CVE-2019-1062\",\n \"CVE-2019-1063\", \"CVE-2019-1067\", \"CVE-2019-1071\", \"CVE-2019-1073\",\n \"CVE-2019-1074\", \"CVE-2019-1085\", \"CVE-2019-1086\", \"CVE-2019-1087\",\n \"CVE-2019-1088\", \"CVE-2019-1089\", \"CVE-2019-1090\", \"CVE-2019-1091\",\n \"CVE-2019-1092\", \"CVE-2019-1093\", \"CVE-2019-1094\", \"CVE-2019-1095\",\n \"CVE-2019-1096\", \"CVE-2019-1097\", \"CVE-2019-1102\", \"CVE-2019-1103\",\n \"CVE-2019-1104\", \"CVE-2019-1106\", \"CVE-2019-1107\", \"CVE-2019-1108\",\n \"CVE-2019-1117\", \"CVE-2019-1118\", \"CVE-2019-1119\", \"CVE-2019-1120\",\n \"CVE-2019-1121\", \"CVE-2019-1122\", \"CVE-2019-1123\", \"CVE-2019-1124\",\n \"CVE-2019-1125\", \"CVE-2019-1126\", \"CVE-2019-1127\", \"CVE-2019-1128\",\n \"CVE-2019-1129\", \"CVE-2019-1130\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_tag(name:\"last_modification\", value:\"2020-07-17 05:57:41 +0000 (Fri, 17 Jul 2020)\");\n script_tag(name:\"creation_date\", value:\"2019-07-10 08:56:08 +0530 (Wed, 10 Jul 2019)\");\n script_name(\"Microsoft Windows Multiple Vulnerabilities (KB4507453)\");\n\n script_tag(name:\"summary\", value:\"This host is missing a critical security\n update according to Microsoft KB4507453\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present\n on the target host.\");\n\n script_tag(name:\"insight\", value:\"Multiple flaws exist due to,\n\n - SymCrypt improperly handles a specially crafted digital signature.\n\n - Scripting engine improperly handles objects in memory in Microsoft browsers.\n\n - DirectWrite improperly handles objects in memory.\n\n - Windows RDP client improperly discloses the contents of its memory.\n\n - Windows Graphics Device Interface (GDI) improperly handles objects in\n the memory.\n\n - Kernel Information Disclosure Vulnerability (SWAPGS Attack).\n\n Please see the references for more information about the vulnerabilities.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation will allow an\n attacker to execute arbitrary code in kernel mode, elevate privileges\n by escaping a sandbox, gain access to sensitive information and conduct\n denial-of-service.\");\n\n script_tag(name:\"affected\", value:\"- Microsoft Windows 10 Version 1903 for 32-bit Systems\n\n - Microsoft Windows 10 Version 1903 for x64-based Systems\");\n\n script_tag(name:\"solution\", value:\"The vendor has released updates. Please see\n the references for more information.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_xref(name:\"URL\", value:\"https://support.microsoft.com/en-us/help/4507453\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2019 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"smb_reg_service_pack.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\n exit(0);\n}\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win10:1, win10x64:1) <= 0){\n exit(0);\n}\n\nsysPath = smb_get_system32root();\nif(!sysPath)\n exit(0);\n\nedgeVer = fetch_file_version(sysPath:sysPath, file_name:\"edgehtml.dll\");\nif(!edgeVer)\n exit(0);\n\nif(version_in_range(version:edgeVer, test_version:\"11.0.18362.0\", test_version2:\"11.0.18362.238\")) {\n report = report_fixed_ver(file_checked:sysPath + \"\\Edgehtml.dll\",\n file_version:edgeVer, vulnerable_range:\"11.0.18362.0 - 11.0.18362.238\");\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-07-21T20:40:53", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-0683", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-1095", "CVE-2019-0999", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "description": "This host is missing a critical security\n update according to Microsoft KB4507455", "modified": "2020-07-17T00:00:00", "published": "2019-07-10T00:00:00", "id": "OPENVAS:1361412562310815400", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310815400", "type": "openvas", "title": "Microsoft Windows Multiple Vulnerabilities (KB4507455)", "sourceData": "# Copyright (C) 2019 Greenbone Networks GmbH\n# Some text descriptions might be excerpted from (a) referenced\n# source(s), and are Copyright (C) by the respective right holder(s).\n#\n# SPDX-License-Identifier: GPL-2.0-or-later\n#\n# This program is free software; you can redistribute it and/or\n# modify it under the terms of the GNU General Public License\n# as published by the Free Software Foundation; either version 2\n# of the License, or (at your option) any later version.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.815400\");\n script_version(\"2020-07-17T05:57:41+0000\");\n script_cve_id(\"CVE-2019-0865\", \"CVE-2019-0880\", \"CVE-2019-0887\", \"CVE-2019-1097\",\n \"CVE-2019-1102\", \"CVE-2019-0966\", \"CVE-2019-0999\", \"CVE-2019-1001\",\n \"CVE-2019-1004\", \"CVE-2019-1103\", \"CVE-2019-1104\", \"CVE-2019-1106\",\n \"CVE-2019-1107\", \"CVE-2019-1006\", \"CVE-2019-1108\", \"CVE-2019-1113\",\n \"CVE-2019-1037\", \"CVE-2019-1056\", \"CVE-2019-1059\", \"CVE-2019-1062\",\n \"CVE-2019-1063\", \"CVE-2019-1067\", \"CVE-2019-1117\", \"CVE-2019-1118\",\n \"CVE-2019-1119\", \"CVE-2019-1120\", \"CVE-2019-1121\", \"CVE-2019-1122\",\n \"CVE-2019-1123\", \"CVE-2019-1124\", \"CVE-2019-1071\", \"CVE-2019-1073\",\n \"CVE-2019-1127\", \"CVE-2019-1128\", \"CVE-2019-1129\", \"CVE-2019-1130\",\n \"CVE-2019-1074\", \"CVE-2019-1083\", \"CVE-2019-1085\", \"CVE-2019-1086\",\n \"CVE-2019-1087\", \"CVE-2019-1088\", \"CVE-2019-1089\", \"CVE-2019-1091\",\n \"CVE-2019-1092\", \"CVE-2019-1095\", \"CVE-2019-1096\", \"CVE-2019-1093\",\n \"CVE-2019-1094\", \"CVE-2019-0683\", \"CVE-2019-1125\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_tag(name:\"last_modification\", value:\"2020-07-17 05:57:41 +0000 (Fri, 17 Jul 2020)\");\n script_tag(name:\"creation_date\", value:\"2019-07-10 09:30:27 +0530 (Wed, 10 Jul 2019)\");\n script_name(\"Microsoft Windows Multiple Vulnerabilities (KB4507455)\");\n\n script_tag(name:\"summary\", value:\"This host is missing a critical security\n update according to Microsoft KB4507455\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present\n on the target host.\");\n\n script_tag(name:\"insight\", value:\"Multiple flaws exist due to,\n\n - SymCrypt improperly handles a specially crafted digital signature.\n\n - Scripting engine improperly handles objects in memory in Microsoft browsers.\n\n - Windows RDP client improperly discloses the contents of its memory.\n\n - Windows Graphics Device Interface (GDI) improperly handles objects in\n the memory.\n\n - An elevation of privilege exists in Windows Audio Service.\n\n - Kernel Information Disclosure Vulnerability (SWAPGS Attack).\n\n Please see the references for more information about the vulnerabilities.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation will allow an\n attacker to execute arbitrary code in kernel mode, elevate privileges\n by escaping a sandbox, gain access to sensitive information, conduct\n denial-of-service and take control of the affected system.\");\n\n script_tag(name:\"affected\", value:\"- Microsoft Windows 10 Version 1709 for 32-bit Systems\n\n - Microsoft Windows 10 Version 1709 for 64-based Systems\");\n\n script_tag(name:\"solution\", value:\"The vendor has released updates. Please see\n the references for more information.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_xref(name:\"URL\", value:\"https://support.microsoft.com/en-us/help/4507455\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2019 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"smb_reg_service_pack.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\n exit(0);\n}\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win10:1, win10x64:1) <= 0){\n exit(0);\n}\n\nsysPath = smb_get_system32root();\nif(!sysPath)\n exit(0);\n\nedgeVer = fetch_file_version(sysPath:sysPath, file_name:\"edgehtml.dll\");\nif(!edgeVer)\n exit(0);\n\nif(version_in_range(version:edgeVer, test_version:\"11.0.16299.0\", test_version2:\"11.0.16299.1267\")) {\n report = report_fixed_ver(file_checked:sysPath + \"\\Edgehtml.dll\",\n file_version:edgeVer, vulnerable_range:\"11.0.16299.0 - 11.0.16299.1267\");\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-07-21T20:40:54", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-0683", "CVE-2019-1090", "CVE-2019-1126", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-0811", "CVE-2019-1095", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-0785", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-0975", "CVE-2019-1056", "CVE-2019-1092", "CVE-2019-1125"], "description": "This host is missing a critical security\n update according to Microsoft KB4507469", "modified": "2020-07-17T00:00:00", "published": "2019-07-10T00:00:00", "id": "OPENVAS:1361412562310815408", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310815408", "type": "openvas", "title": "Microsoft Windows Multiple Vulnerabilities (KB4507469)", "sourceData": "# Copyright (C) 2019 Greenbone Networks GmbH\n# Some text descriptions might be excerpted from (a) referenced\n# source(s), and are Copyright (C) by the respective right holder(s).\n#\n# SPDX-License-Identifier: GPL-2.0-or-later\n#\n# This program is free software; you can redistribute it and/or\n# modify it under the terms of the GNU General Public License\n# as published by the Free Software Foundation; either version 2\n# of the License, or (at your option) any later version.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.815408\");\n script_version(\"2020-07-17T05:57:41+0000\");\n script_cve_id(\"CVE-2019-0785\", \"CVE-2019-0811\", \"CVE-2019-0865\", \"CVE-2019-0880\",\n \"CVE-2019-0887\", \"CVE-2019-1097\", \"CVE-2019-1102\", \"CVE-2019-0966\",\n \"CVE-2019-0975\", \"CVE-2019-1001\", \"CVE-2019-1004\", \"CVE-2019-1103\",\n \"CVE-2019-1104\", \"CVE-2019-1106\", \"CVE-2019-1107\", \"CVE-2019-1108\",\n \"CVE-2019-1006\", \"CVE-2019-1037\", \"CVE-2019-1056\", \"CVE-2019-1059\",\n \"CVE-2019-1062\", \"CVE-2019-1063\", \"CVE-2019-1067\", \"CVE-2019-1117\",\n \"CVE-2019-1118\", \"CVE-2019-1119\", \"CVE-2019-1120\", \"CVE-2019-1121\",\n \"CVE-2019-1122\", \"CVE-2019-1123\", \"CVE-2019-1071\", \"CVE-2019-1073\",\n \"CVE-2019-1124\", \"CVE-2019-1126\", \"CVE-2019-1127\", \"CVE-2019-1128\",\n \"CVE-2019-1129\", \"CVE-2019-1130\", \"CVE-2019-1074\", \"CVE-2019-1085\",\n \"CVE-2019-1086\", \"CVE-2019-1087\", \"CVE-2019-1088\", \"CVE-2019-1089\",\n \"CVE-2019-1090\", \"CVE-2019-1091\", \"CVE-2019-1092\", \"CVE-2019-1095\",\n \"CVE-2019-1096\", \"CVE-2019-1093\", \"CVE-2019-1094\", \"CVE-2019-0683\",\n \"CVE-2019-1125\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_tag(name:\"last_modification\", value:\"2020-07-17 05:57:41 +0000 (Fri, 17 Jul 2020)\");\n script_tag(name:\"creation_date\", value:\"2019-07-10 08:23:27 +0530 (Wed, 10 Jul 2019)\");\n script_name(\"Microsoft Windows Multiple Vulnerabilities (KB4507469)\");\n\n script_tag(name:\"summary\", value:\"This host is missing a critical security\n update according to Microsoft KB4507469\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present\n on the target host.\");\n\n script_tag(name:\"insight\", value:\"Multiple flaws exist due to,\n\n - SymCrypt improperly handles a specially crafted digital signature.\n\n - Scripting engine improperly handles objects in memory in Microsoft browsers.\n\n - DirectWrite improperly handles objects in memory.\n\n - Windows RDP client improperly discloses the contents of its memory.\n\n - Active Directory Federation Services (ADFS) improperly updates its list\n of banned IP addresses.\n\n - Kernel Information Disclosure Vulnerability (SWAPGS Attack).\n\n Please see the references for more information about the vulnerabilities.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation will allow attackers\n to run arbitrary code, obtain information to further compromise the user's\n system, conduct denial-of-service and take control of the affected system.\");\n\n script_tag(name:\"affected\", value:\"- Microsoft Windows Server 2019\n\n - Microsoft Windows 10 Version 1809 for 32-bit Systems\n\n - Microsoft Windows 10 Version 1809 for x64-based Systems\");\n\n script_tag(name:\"solution\", value:\"The vendor has released updates.\n Please see the references for more information.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_xref(name:\"URL\", value:\"https://support.microsoft.com/en-us/help/4507469\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2019 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"smb_reg_service_pack.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\n exit(0);\n}\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win10:1, win10x64:1) <= 0){\n exit(0);\n}\n\nsysPath = smb_get_system32root();\nif(!sysPath)\n exit(0);\n\nedgeVer = fetch_file_version(sysPath:sysPath, file_name:\"edgehtml.dll\");\nif(!edgeVer)\n exit(0);\n\nif(version_in_range(version:edgeVer, test_version:\"11.0.17763.0\", test_version2:\"11.0.17763.614\")) {\n report = report_fixed_ver(file_checked:sysPath + \"\\Edgehtml.dll\",\n file_version:edgeVer, vulnerable_range:\"11.0.17763.0 - 11.0.17763.614\");\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2020-07-21T20:40:50", "bulletinFamily": "scanner", "cvelist": ["CVE-2019-1123", "CVE-2019-0683", "CVE-2019-1090", "CVE-2019-1126", "CVE-2019-1093", "CVE-2019-0887", "CVE-2019-1097", "CVE-2019-1122", "CVE-2019-1106", "CVE-2019-1086", "CVE-2019-1063", "CVE-2019-1004", "CVE-2019-1037", "CVE-2019-1120", "CVE-2019-1103", "CVE-2019-0865", "CVE-2019-1128", "CVE-2019-1127", "CVE-2019-1089", "CVE-2019-0880", "CVE-2019-1087", "CVE-2019-1104", "CVE-2019-1121", "CVE-2019-1074", "CVE-2019-1094", "CVE-2019-1059", "CVE-2019-1067", "CVE-2019-1129", "CVE-2019-1117", "CVE-2019-1085", "CVE-2019-1006", "CVE-2019-1088", "CVE-2019-0811", "CVE-2019-1095", "CVE-2019-0999", "CVE-2019-1096", "CVE-2019-0966", "CVE-2019-0785", "CVE-2019-1107", "CVE-2019-1071", "CVE-2019-1001", "CVE-2019-1130", "CVE-2019-1062", "CVE-2019-1124", "CVE-2019-1108", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1113", "CVE-2019-1091", "CVE-2019-1073", "CVE-2019-1102", "CVE-2019-0975", "CVE-2019-1056", "CVE-2019-1083", "CVE-2019-1092", "CVE-2019-1125"], "description": "This host is missing a critical security\n update according to Microsoft KB4507435", "modified": "2020-07-17T00:00:00", "published": "2019-07-10T00:00:00", "id": "OPENVAS:1361412562310815401", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310815401", "type": "openvas", "title": "Microsoft Windows Multiple Vulnerabilities (KB4507435)", "sourceData": "# Copyright (C) 2019 Greenbone Networks GmbH\n# Some text descriptions might be excerpted from (a) referenced\n# source(s), and are Copyright (C) by the respective right holder(s).\n#\n# SPDX-License-Identifier: GPL-2.0-or-later\n#\n# This program is free software; you can redistribute it and/or\n# modify it under the terms of the GNU General Public License\n# as published by the Free Software Foundation; either version 2\n# of the License, or (at your option) any later version.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.815401\");\n script_version(\"2020-07-17T05:57:41+0000\");\n script_cve_id(\"CVE-2019-0785\", \"CVE-2019-0811\", \"CVE-2019-0865\", \"CVE-2019-0880\",\n \"CVE-2019-0887\", \"CVE-2019-1102\", \"CVE-2019-0966\", \"CVE-2019-0975\",\n \"CVE-2019-0999\", \"CVE-2019-1001\", \"CVE-2019-1004\", \"CVE-2019-1103\",\n \"CVE-2019-1104\", \"CVE-2019-1106\", \"CVE-2019-1107\", \"CVE-2019-1006\",\n \"CVE-2019-1108\", \"CVE-2019-1037\", \"CVE-2019-1056\", \"CVE-2019-1113\",\n \"CVE-2019-1059\", \"CVE-2019-1062\", \"CVE-2019-1063\", \"CVE-2019-1067\",\n \"CVE-2019-1117\", \"CVE-2019-1118\", \"CVE-2019-1119\", \"CVE-2019-1120\",\n \"CVE-2019-1121\", \"CVE-2019-1122\", \"CVE-2019-1123\", \"CVE-2019-1124\",\n \"CVE-2019-1071\", \"CVE-2019-1073\", \"CVE-2019-1126\", \"CVE-2019-1127\",\n \"CVE-2019-1128\", \"CVE-2019-1129\", \"CVE-2019-1130\", \"CVE-2019-1074\",\n \"CVE-2019-1083\", \"CVE-2019-1085\", \"CVE-2019-1086\", \"CVE-2019-1087\",\n \"CVE-2019-1088\", \"CVE-2019-1089\", \"CVE-2019-1090\", \"CVE-2019-1091\",\n \"CVE-2019-1092\", \"CVE-2019-1095\", \"CVE-2019-1096\", \"CVE-2019-1097\",\n \"CVE-2019-1093\", \"CVE-2019-1094\", \"CVE-2019-0683\", \"CVE-2019-1125\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_tag(name:\"last_modification\", value:\"2020-07-17 05:57:41 +0000 (Fri, 17 Jul 2020)\");\n script_tag(name:\"creation_date\", value:\"2019-07-10 09:41:08 +0530 (Wed, 10 Jul 2019)\");\n script_name(\"Microsoft Windows Multiple Vulnerabilities (KB4507435)\");\n\n script_tag(name:\"summary\", value:\"This host is missing a critical security\n update according to Microsoft KB4507435\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present\n on the target host.\");\n\n script_tag(name:\"insight\", value:\"Multiple flaws exist due to,\n\n - SymCrypt improperly handles a specially crafted digital signature.\n\n - Scripting engine improperly handles objects in memory in Microsoft browsers.\n\n - Windows RDP client improperly discloses the contents of its memory.\n\n - Windows Graphics Device Interface (GDI) improperly handles objects in\n the memory.\n\n - An elevation of privilege exists in Windows Audio Service.\n\n - Kernel Information Disclosure Vulnerability (SWAPGS Attack).\n\n Please see the references for more information about the vulnerabilities.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation will allow an\n attacker to execute arbitrary code in kernel mode, elevate privileges\n by escaping a sandbox, gain access to sensitive information, conduct\n denial of service and could take control of the affected system.\");\n\n script_tag(name:\"affected\", value:\"- Microsoft Windows 10 Version 1803 for 32-bit Systems\n\n - Microsoft Windows 10 Version 1803 for x64-based Systems\");\n\n script_tag(name:\"solution\", value:\"The vendor has released updates. Please see\n the references for more information.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_xref(name:\"URL\", value:\"https://support.microsoft.com/en-us/help/4507435\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2019 Greenbone Networks GmbH\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"smb_reg_service_pack.nasl\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\n exit(0);\n}\n\ninclude(\"smb_nt.inc\");\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\ninclude(\"secpod_smb_func.inc\");\n\nif(hotfix_check_sp(win10:1, win10x64:1) <= 0){\n exit(0);\n}\n\nsysPath = smb_get_system32root();\nif(!sysPath)\n exit(0);\n\nedgeVer = fetch_file_version(sysPath:sysPath, file_name:\"edgehtml.dll\");\nif(!edgeVer)\n exit(0);\n\nif(version_in_range(version:edgeVer, test_version:\"11.0.17134.0\", test_version2:\"11.0.17134.884\")) {\n report = report_fixed_ver(file_checked:sysPath + \"\\Edgehtml.dll\",\n file_version:edgeVer, vulnerable_range:\"11.0.17134.0 - 11.0.17134.884\");\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "talosblog": [{"lastseen": "2019-07-17T08:29:26", "bulletinFamily": "blog", "cvelist": ["CVE-2018-15664", "CVE-2019-0709", "CVE-2019-0722", "CVE-2019-0785", "CVE-2019-0811", "CVE-2019-0865", "CVE-2019-0880", "CVE-2019-0887", "CVE-2019-0962", "CVE-2019-0966", "CVE-2019-0975", "CVE-2019-0985", "CVE-2019-0990", "CVE-2019-0999", "CVE-2019-1001", "CVE-2019-1004", "CVE-2019-1006", "CVE-2019-1037", "CVE-2019-1038", "CVE-2019-1051", "CVE-2019-1052", "CVE-2019-1056", "CVE-2019-1059", "CVE-2019-1062", "CVE-2019-1063", "CVE-2019-1067", "CVE-2019-1068", "CVE-2019-1071", "CVE-2019-1072", "CVE-2019-1073", "CVE-2019-1074", "CVE-2019-1075", "CVE-2019-1076", "CVE-2019-1077", "CVE-2019-1079", "CVE-2019-1082", "CVE-2019-1083", "CVE-2019-1084", "CVE-2019-1085", "CVE-2019-1086", "CVE-2019-1087", "CVE-2019-1088", "CVE-2019-1089", "CVE-2019-1090", "CVE-2019-1091", "CVE-2019-1092", "CVE-2019-1093", "CVE-2019-1094", "CVE-2019-1095", "CVE-2019-1096", "CVE-2019-1097", "CVE-2019-1098", "CVE-2019-1099", "CVE-2019-1100", "CVE-2019-1101", "CVE-2019-1102", "CVE-2019-1103", "CVE-2019-1104", "CVE-2019-1106", "CVE-2019-1107", "CVE-2019-1108", "CVE-2019-1109", "CVE-2019-1110", "CVE-2019-1111", "CVE-2019-1112", "CVE-2019-1113", "CVE-2019-1116", "CVE-2019-1117", "CVE-2019-1118", "CVE-2019-1119", "CVE-2019-1120", "CVE-2019-1121", "CVE-2019-1122", "CVE-2019-1123", "CVE-2019-1124", "CVE-2019-1126", "CVE-2019-1127", "CVE-2019-1128", "CVE-2019-1129", "CVE-2019-1130", "CVE-2019-1132", "CVE-2019-1134", "CVE-2019-1136", "CVE-2019-1137"], "description": "[](<http://3.bp.blogspot.com/-bIERk6jqSvs/XKypl8tltSI/AAAAAAAAFxU/d9l6_EW1Czs7DzBngmhg8pjdPfhPAZ3yACK4BGAYYCw/s1600/recurring%2Bblog%2Bimages_patch%2Btuesday.jpg>) \nMicrosoft released its monthly security update today, disclosing a variety of vulnerabilities in several of its products. The latest Patch Tuesday covers 77 vulnerabilities, 16 of which are rated \u201ccritical,\" 60 that are considered \"important\" and one \"moderate.\" \n \nThis month\u2019s security update covers security issues in a variety of Microsoft\u2019s products, including the Chakra scripting engine, Internet Explorer and the Windows Server DHCP service. For more on our coverage of these bugs, check out the SNORT\u00ae blog post [here](<https://blog.snort.org/2019/07/snort-rule-update-for-july-9-2019.html>), covering all of the new rules we have for this release. \n \n\n\n### Critical vulnerabilities\n\nMicrosoft disclosed 16 critical vulnerabilities this month, nine of which we will highlight below. \n \n[CVE-2019-0785](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0785>) is a memory corruption vulnerability in the Windows Server DHCP service. The bug arises when specially crafted packets are sent to a DHCP failover server. A malicious user could exploit this vulnerability by sending a specially crafted packet to a DHCP over failover mode. This could allow them to gain the ability to run arbitrary code on the DHCP failover server or cause the DHCP server to become unresponsive. \n \n[CVE-2019-1001](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1001>) and [CVE-2019-1004](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1004>) are both memory corruption vulnerabilities that exist in the way the scripting engine handles objects in memory in Microsoft browsers. These bugs could corrupt memory on machines in such a way that attackers could gain the ability to execute arbitrary code in the context of the current user. An attacker could exploit these bugs by tricking a user into visiting a specially crafted, malicious web page through Internet Explorer. They could also embed an ActiveX control marked \"safe for initialization\" in an application or Microsoft Office document that uses the Internet Explorer-rendering engine. \n \n[CVE-2019-1062](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1062>), [CVE-2019-1092](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1092>), [CVE-2019-1103](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1103>), [CVE-2019-1106](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1106>) and [CVE-2019-1107](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1107>) are all memory corruption vulnerabilities in the Chakra Scripting Engine that could allow an attacker to gain the ability to execute arbitrary code on the victim's machine. An attacker could exploit these bugs by tricking a user into visiting a specially crafted, malicious web page on Microsoft Edge, or by visiting a site with attacker-created content. \n \n[CVE-2019-1113 ](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1113>)is a remote code execution vulnerability in the .NET Framework. The vulnerability exists in the way the software checks the source markup of a file. An attacker could exploit this vulnerability by supplying the user with a specially crafted file, and then tricking them into opening it using an affected version of the .NET Framework. An attacker could then gain the ability to execute arbitrary code in the context of the current user. \n \nThe other critical vulnerabilities are: \n\n\n[](<http://cve-2019-0709%20cve-2019-0722%20%20%20cve-2019-0985%20%20%20cve-2019-0990%20%20%20%20%20%20%20cve-2019-1038%20cve-2019-1051%20cve-2019-1052%20cve-2019-0709/>)\n * [CVE-2019-1006](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1006>)[](<http://cve-2019-0709%20cve-2019-0722%20%20%20cve-2019-0985%20%20%20cve-2019-0990%20%20%20%20%20%20%20cve-2019-1038%20cve-2019-1051%20cve-2019-1052%20cve-2019-0709/>)\n * [CVE-2019-1056](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1056>)\n * [CVE-2019-1059](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1059>)\n * [CVE-2019-1063](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1063>)\n * [CVE-2019-1072](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1072>)\n * [CVE-2019-1102](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1102>)\n * [CVE-2019-1104](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1104>)\n\n### Important vulnerabilities\n\nThis release also contains 60 important vulnerabilities, two of which we will highlight below. \n \n[CVE-2018-15664](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15664>) is an elevation of privilege vulnerability in Docker that affects Microsoft Azure internet-of-things edge devices and Azure Kubernetes Service. The bug allows a malicious or compromised container to acquire full read/write access on the host operating system where the container is running. While a fix is still ongoing in Docker, Microsoft recommends customers do not use the Docker copy command on their AKS clusters and the Azure IoT devices. \n \n[CVE-2019-1132](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1132>) is an elevation of privilege vulnerability in Windows when the Win32k component fails to properly handle objects in memory. An attacker could exploit this bug to run arbitrary code in kernel mode. Microsoft disclosed that this vulnerability has been exploited in the wild. \n \nThe other important vulnerabilities are: \n\n\n * [CVE-2019-0811](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0811>)\n * [CVE-2019-0865](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0865>)\n * [CVE-2019-0880](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0880>)\n * [CVE-2019-0887](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0887>)\n * [CVE-2019-0962](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0962>)\n * [CVE-2019-0966](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0966>)\n * [CVE-2019-0975](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0975>)\n * [CVE-2019-0999](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0999>)\n * [CVE-2019-1037](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1037>)\n * [CVE-2019-1067](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1067>)\n * [CVE-2019-1068](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068>)\n * [CVE-2019-1071](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1071>)\n * [CVE-2019-1073](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1073>)\n * [CVE-2019-1074](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1074>)\n * [CVE-2019-1076](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1076>)\n * [CVE-2019-1077](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1077>)\n * [CVE-2019-1079](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1079>)\n * [CVE-2019-1082](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1082>)\n * [CVE-2019-1083](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1083>)\n * [CVE-2019-1084](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1084>)\n * [CVE-2019-1085](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1085>)\n * [CVE-2019-1086](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1086>)\n * [CVE-2019-1087](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1087>)\n * [CVE-2019-1088](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1088>)\n * [CVE-2019-1089](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1089>)\n * [CVE-2019-1090](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1090>)\n * [CVE-2019-1091](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1091>)\n * [CVE-2019-1093](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1093>)\n * [CVE-2019-1094](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1094>)\n * [CVE-2019-1095](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1095>)\n * [CVE-2019-1096](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1096>)\n * [CVE-2019-1097](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1097>)\n * [CVE-2019-1098](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1098>)\n * [CVE-2019-1099](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1099>)\n * [CVE-2019-1100](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1100>)\n * [CVE-2019-1101](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1101>)\n * [CVE-2019-1108](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1108>)\n * [CVE-2019-1109](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1109>)\n * [CVE-2019-1110](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1110>)\n * [CVE-2019-1111](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1111>)\n * [CVE-2019-1112](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1112>)\n * [CVE-2019-1116](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1116>)\n * [CVE-2019-1117](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1117>)\n * [CVE-2019-1118](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1118>)\n * [CVE-2019-1119](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1119>)\n * [CVE-2019-1120](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1120>)\n * [CVE-2019-1121](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1121>)\n * [CVE-2019-1122](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1122>)\n * [CVE-2019-1123](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1123>)\n * [CVE-2019-1124](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1124>)\n * [CVE-2019-1126](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1126>)\n * [CVE-2019-1127](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1127>)\n * [CVE-2019-1128](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1128>)\n * [CVE-2019-1129](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1129>)\n * [CVE-2019-1130](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1130>)\n * [CVE-2019-1134](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1134>)\n * [CVE-2019-1136](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1136>)\n * [CVE-2019-1137](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1137>)\n\n### Moderate vulnerability\n\nThere is one moderate vulnerability, [CVE-2019-1075](<https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1075>), which is an information disclosure vulnerability in Windows Event Manager. \n\n\n### Coverage \n\nIn response to these vulnerability disclosures, Talos is releasing the following SNORT\u24c7 rules that detect attempts to exploit them. Please note that additional rules may be released at a future date and current rules are subject to change pending additional information. Firepower customers should use the latest update to their ruleset by updating their SRU. Open Source Snort Subscriber Rule Set customers can stay up-to-date by downloading the latest rule pack available for purchase on Snort.org. \n \nSnort rules: [45142, 45143, 46548, 46549, 49380, 49381, 50198, 50199, 50662 - 50683](<https://snort.org/advisories/talos-rules-2019-07-09>)\n\n", "modified": "2019-07-09T11:51:34", "published": "2019-07-09T11:51:34", "id": "TALOSBLOG:07D81B04EFE21AC0E3C8DD9F1F76E7A4", "href": "http://feedproxy.google.com/~r/feedburner/Talos/~3/RHbSOXkTWQA/microsoft-patch-tuesday-july-2019.html", "type": "talosblog", "title": "Microsoft Patch Tuesday \u2014 July 2019: Vulnerability disclosures and Snort coverage", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}]}