Page 13 of 82 results (0.017 seconds)

CVSS: 5.5EPSS: 1%CPEs: 25EXPL: 1

Graphics Device Interface (aka GDI or 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; Windows 10 Gold, 1511, and 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; Live Meeting 2007 Console; .NET Framework 3.0 SP2, 3.5, 3.5.1, 4.5.2, and 4.6; and Silverlight 5 allows remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "True Type Font Parsing Information Disclosure Vulnerability." Graphics Device Interface (también conocido como GDI o GDI+) en Microsoft Windows Vista SP2; Windows Server 2008 SP2 y R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold y R2; Windows RT 8.1; Windows 10 Gold, 1511 y 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; Live Meeting 2007 Console; .NET Framework 3.0 SP2, 3.5, 3.5.1, 4.5.2 y 4.6; y Silverlight 5 permite a atacantes remotos eludir el mecanismo de protección ASLR a través de vectores no especificados, vulnerabilidad también conocida como "True Type Font Parsing Information Disclosure Vulnerability". Windows Kernel win32k.sys suffers from a TTF font procession out-of-bounds read in the RCVT TrueType instruction handler. • https://www.exploit-db.com/exploits/40598 http://www.securityfocus.com/bid/93385 http://www.securitytracker.com/id/1036988 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-120 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.5EPSS: 9%CPEs: 6EXPL: 0

Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, and 4.6.1 allows remote attackers to read arbitrary files via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, aka ".NET Information Disclosure Vulnerability." Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6 y 4.6.1 permite a atacantes remotos leer archivos arbitrario a través de datos XML que contienen una declaración de entidad externa en conjunción con una referencia a entidad, relacionado con un caso XML External Entity (XXE), también conocida como ".NET Information Disclosure Vulnerability". • http://www.securityfocus.com/bid/91601 http://www.securitytracker.com/id/1036291 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-091 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 5.9EPSS: 0%CPEs: 7EXPL: 0

Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, and 4.6.1 allows man-in-the-middle attackers to obtain sensitive cleartext information via vectors involving injection of cleartext data into the client-server data stream, aka "TLS/SSL Information Disclosure Vulnerability." Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6 y 4.6.1 permite a atacantes man-in-the-middle obtener información sensible en texto plano a través de vectores que implican la inyección de datos en texto claro en el flujo de datos cliente-servidor, también conocido como "TLS/SSL Information Disclosure Vulnerability". • http://www.securityfocus.com/bid/90026 http://www.securitytracker.com/id/1035842 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-065 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.8EPSS: 8%CPEs: 2EXPL: 0

Microsoft .NET Framework 4.6 and 4.6.1 mishandles library loading, which allows local users to gain privileges via a crafted application, aka ".NET Framework Remote Code Execution Vulnerability." Microsoft .NET Framework 4.6 y 4.6.1 no maneja correctamente la carga de librerías, lo que permite a usuarios locales obtener privilegios a través de una aplicación manipulada, también conocida como ".NET Framework Remote Code Execution Vulnerability". This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Microsoft .NET Framework. User interaction is required to exploit this vulnerability in that the target must visit a malicious web page or open a malicious directory or device. The specific flaw exists within the handling of a specific named DLL used by .NET Framework. By providing a directory with this specific DLL, an attacker is able to force the process to load an arbitrary DLL. • http://packetstormsecurity.com/files/136671/.NET-Framework-4.6-DLL-Hijacking.html http://seclists.org/fulldisclosure/2016/Apr/42 http://www.securityfocus.com/archive/1/538063/100/0/threaded http://www.securitytracker.com/id/1035535 http://www.zerodayinitiative.com/advisories/ZDI-16-234 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-041 • CWE-264: Permissions, Privileges, and Access Controls •

CVSS: 10.0EPSS: 1%CPEs: 7EXPL: 0

Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, and 4.6.1 mishandles signature validation for unspecified elements of XML documents, which allows remote attackers to spoof signatures via a modified document, aka ".NET XML Validation Security Feature Bypass." Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, y 4.6.1 no maneja correctamente la validación de firma para elementos no especificados de documentos XML, lo que permite a atacantes remotos suplantar firmas a través de un documento manipulado, también conocido como ".NET XML Validation Security Feature Bypass". • http://www.securityfocus.com/bid/84075 http://www.securitytracker.com/id/1035213 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-035 • CWE-20: Improper Input Validation •