SB2019031313 - Multiple vulnerabilities in Microsoft Windows
Published: March 13, 2019 Updated: March 17, 2019
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 9 secuirty vulnerabilities.
1) Buffer overflow (CVE-ID: CVE-2019-0696)
The vulnerability allows a local user to escalate privileges on the system.
The vulnerability exists due to a boundary error when the Windows kernel fails to properly handle objects in memory. A local user can use a specially specially crafted application to trigger memory corruption and execute arbitrary code on the target system.
Successful exploitation of this vulnerability may result in complete compromise of vulnerable system.
2) Buffer overflow (CVE-ID: CVE-2019-0754)
The vulnerability allows a local user to perform denial of service (DoS) attack.
The vulnerability exists due to a boundary error when Windows improperly handles objects in memory. A local user can use a specially specially crafted application to trigger memory corruption and cause the system to stop responding.
Successful exploitation of this vulnerability may result in a denial of service (DoS) attack.
3) Out-of-bounds read (CVE-ID: CVE-2019-0702)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the Windows kernel improperly handles objects in memory. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
4) Out-of-bounds read (CVE-ID: CVE-2019-0774)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the Windows GDI component discloses the contents of its memory. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
5) Out-of-bounds read (CVE-ID: CVE-2019-0614)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the Windows GDI component discloses the contents of its memory. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
6) Out-of-bounds read (CVE-ID: CVE-2019-0782)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the Windows kernel fails to properly initialize a memory address. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
7) Out-of-bounds read (CVE-ID: CVE-2019-0776)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the win32k component improperly provides kernel information. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
8) Out-of-bounds read (CVE-ID: CVE-2019-0755)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the Windows kernel improperly handles objects in memory. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
9) Out-of-bounds read (CVE-ID: CVE-2019-0767)
The vulnerability allows a local user to gain access to potentially sensitive information.
The vulnerability exists due to a boundary condition due to the way the Windows kernel improperly initializes objects in memory. A local user can use a specially specially crafted application to trigger out-of-bounds read error and read contents of memory on the system.
Remediation
Install update from vendor's website.
References
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0696
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0754
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0702
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0774
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0614
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0782
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0776
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0755
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0767