Graphics Processing Units in Vulnerable Lane

    In the past, Graphics Processing Unit (GPU) drivers weren’t a typical target for system exploitation, but this has changed in recent years. Many computing applications from desktop to server require more graphics horsepower than ever before and, as such, discrete GPUs are more common than ever. Laptops are even often configured with high-performance GPUs included instead of the basic CPU embedded graphics chipsets of the past. Modern GPUs are highly complicated components requiring complex system drivers to maximize the GPUs capability.

    As system complexity increases continuously, so does the potential for finding a way to exploit the system. This effect is multiplied because GPU drivers usually run in the highest privilege ring of the system, kernel mode. This week, graphics chip maker Nvidia patched its drivers to fix two high security vulnerabilities as well as several lower severity vulnerabilities.

    The first vulnerability patched by Nvidia this week relates to the Nvidia Control Panel component. This software is bundled as part of the Nvidia graphics driver package and allows for adjusting settings related to the graphics subsystem. The vulnerability, assigned CVE-2020-5962, allows for a local attacker to corrupt critical system files, leading to denial of service or escalation of privileges. Little information is available about the vulnerability specifics but systems running this software should be updated to prevent local attacks against the machine.

    CUDA is a subsystem in Nvidia drivers that allows for non-graphics use of the high-performance processing units for machine learning or artificial intelligence programs. These applications benefit greatly from the highly-parallelized nature of graphics hardware and typically use high-end graphics cards for their processing. The second high security vulnerability, CVE-2020-5963, is in the CUDA component of the graphics driver. Again, little information is available about the specifics, but the issue appears to stem from a mistake in the access control security in the Inter Process Communication APIs. This vulnerability could lead to arbitrary code execution from a lower privilege process in the context of a high privilege process.

    Other Nvidia vulnerabilities patched this week are classified as medium severity. CVE-2020-5967 and CVE-2020-5965 appear to be similar vulnerabilities in Linux and Windows respectively, which allow for denial of service to the target system. CVE-2020-5964 and CVE-2020-5966 are exclusive to Windows systems and range in severity from denial of service to arbitrary code execution.
As high-performance GPUs become more common in even basic systems it is important to verify that your drivers are being updated in a timely fashion.

Sources:
       
https://threatpost.com/nvidia-windows-gamers-graphics-driver-bugs/156911/

https://nvidia.custhelp.com/app/answers/detail/a_id/5031

Sources:

Netgear Router Vulnerabilities

National Cyber Awareness System:

06/29/2020 03:44 PM EDT
Original
release date: June 29, 2020

    Multiple Netgear router models contain vulnerabilities that a remote
attacker can exploit to take control of an affected device.

    The Cybersecurity and Infrastructure Security Agency (CISA) encourages users
and administrators to update to the most recent firmware version and to replace
end-of-life devices that are no longer supported with security patches. Given
the increase in telework, CISA
recommends that CISOs consider the risk that these vulnerabilities present to
business networks.
See the following products for additional information.

DNS Vulnerability – CVSS – Score of 10

Microsoft has released a
critical patch impacting
all Windows Server Operating System Versions with the DNS role installed. The
included affected operating systems are: 2003 – 2019.

This patch has a significant risk of being exploited, and if an attacker
successfully exploited the vulnerability, they could run arbitrary code in the
context of the Local System Account. As most organizations install the DNS
Server role on their Domain Controller, the attacker would gain full control of
a Domain Controller. Once the attacker has full control of the domain
controller, lateral movement to any Domain joined system is possible.
https://msrc-blog.microsoft.com/2020/07/14/july-2020-security-update-cve-2020-1350-vulnerability-in-windows-domain-name-system-dns-server/
There are no known uses in the wild of this. It is highly recommended you patch
all windows DNS servers (internal and external) that you may own as soon as
possible.

WHAT YOU NEED TO DO

In order to secure your environment as soon as possible, you should complete
the following steps as soon as possible.
 

  1. IDENTIFY –  ALL WINDOWS DNS
    servers in your environment – both internal and external. – You can use
    PowerShell to help
  2. TEST – The applicable monthly
    servicing stack, and cumulative update for the server operating system.
  3. DEPLOY – The applicable patch to all DNS
    servers in your environment as soon as possible.

NIST Releases Draft SP 800-181 Revision 1 for Comment

The National
Initiative for Cybersecurity Education (NICE)
 has released Draft NIST Special Publication (SP)
800-181 Revision 1,
Workforce Framework for Cybersecurity (NICE Framework).
The NICE Framework is a fundamental reference for describing and sharing
information about cybersecurity work in the form of Task Statements and as Work
Roles that perform those tasks. In this revision, several updates have been
made, including:

  • an updated title to be more
    inclusive of the variety of workers who perform cybersecurity work, 
  • definition and normalization of
    key terms,
  • principles that facilitate
    agility, flexibility, interoperability, and modularity,
  • introduction of competencies,
  • and more!

The
public comment period is open through August 28, 2020.
See the publication
details
for a copy of the document and instructions for submitting
comments

Outlook Crashing on Launch

Active Investigation into Outlook Crashing on Launch

There is a new symptom of Outlook is crashing on launch starting 7/15.   A fix has been published but will take time to propagate to worldwide availability.   Outlook will automatically look for the fix on launch, so if this issue persists through multiple launches please use Outlook Web Access for an hour then try again.   
If this issue persists beyond four hours please contact Microsoft Support by whichever means works best for you.
  1. You may see an error such as:
    “Outlook couldn’t start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode.
    Do you want to start in Safe Mode?”
  2. In the event viewer you will see a crash event like:
    1. Faulting application name: OUTLOOK.EXE, version: 16.0.13102.20002, time stamp: 0x5efe7a9e
      Faulting module name: OUTLOOK.EXE, version: 16.0.13102.20002, time stamp: 0x5efe7a9e
      Exception code: 0xc0000005
      Fault offset: 0x00000000001a40fa
      Faulting process id: 0x3f60
      Faulting application start time: 0x01d65ac2602949dd
      Faulting application path: C:Program FilesMicrosoft OfficerootOffice16OUTLOOK.EXE
      Faulting module path: C:Program FilesMicrosoft OfficerootOffice16OUTLOOK.EXE
      Report Id: 81a20cc2-6c7f-4635-90ba-54319c3fce75
      Faulting package full name:
      Faulting package-relative application ID:
       Microsoft suggests users use web and mobile clients until the issue is resolved.
      Title: Users experiencing Outlook connection issues and crashes
      User Impact: Users may experience crashes or may be unable to access Exchange Online via Outlook.
      More info: Our analysis indicates that Outlook on the web and mobile clients are unaffected. Users may be able to leverage those protocols as an alternative means to access email and service features while we remediate this problem.
      Current status: Our initial review of the available data indicates that recently deployed updates are the likely source of the problem. We’re performing an analysis of all recent service updates to isolate the underlying cause of the problem and to determine the most expedient means to restore service.
      Scope of impact: This issue may potentially affect any of your users attempting to use Outlook.
       you could try 

      Open cmd, run:
      cd “Program FilesCommon Filesmicrosoft
      sharedClickToRun”
      then:
      officec2rclient.exe /update user
      updatetoversion=16.0.12827.20470