Veille CVE

Recherche « Microsoft windows 10 1507 »

4 CVE

Critique 1 Élevée 3 Moyenne 0 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « Microsoft windows 10 1507 » ✕
  1. CVE-2023-28252 7.8 Élevée Exploitée Rançongiciel

    Microsoft Windows 10 Version 1809 · Microsoft Windows Server 2019 · Microsoft Windows Server 2019 (Server Core installation) · Microsoft Windows Server 2022

    Windows Common Log File System Driver Elevation of Privilege Vulnerability

  2. CVE-2019-1388 7.8 Élevée Exploitée Rançongiciel

    Microsoft Windows · Microsoft Windows Server · Microsoft Windows 10 Version 1903 for 32-bit Systems · Microsoft Windows 10 Version 1903 for x64-based Systems

    An elevation of privilege vulnerability exists in the Windows Certificate Dialog when it does not properly enforce user privileges, aka 'Windows Certificate Dialog Elevation of Privilege Vulnerability'.

  3. CVE-2017-8543 9.8 Critique Exploitée

    Microsoft Corporation Microsoft Windows · Microsoft windows 10 1507 · Microsoft windows 10 1511 · Microsoft windows 10 1607

    Microsoft Windows XP SP3, Windows XP x64 XP2, Windows Server 2003 SP2, Windows Vista, Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to take control of the affected system when Windows Search fails to handle objects in memory, aka "Windows Search Remote Code Execution Vulnerability".

  4. CVE-2017-0005 7.8 Élevée Exploitée

    Microsoft Corporation Windows GDI · Microsoft windows 10 1507 · Microsoft windows 10 1511 · Microsoft windows 10 1607

    The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607 allows local users to gain privileges via a crafted application, aka "Windows GDI Elevation of Privilege Vulnerability." This vulnerability is different from those described in CVE-2017-0001, CVE-2017-0025, and CVE-2017-0047.