Notification

Icon
Error

Intel Foreshadow Vulnerability

Posted: Monday, August 20, 2018 1:54:28 PM(UTC)
Esben.D

Esben.D

Member Administration Original PosterPosts: 1,982
11
Like
Researchers have identified new vulnerabilities in many Intel processors called Foreshadow or L1TF (L1 Terminal Fault). This vulnerability consists of 3 major vulnerabilities:
  • CVE-2018-3615: Vulnerability in the Intel software guard extension (SGX).
  • CVE-2018-3620: L1 data cache vulnerability on the operating system and system management mode level.
  • CVE-2018-3646: L1 data cache vulnerability on the virtual machine manager.
This vulnerability allows attackers to read data in shared resource environments like cloud and virtual environments from the processor's L1 data cache. You can find the full technical details in the Microsoft analysis on the Intel website and the researcher's website.

All assets shown in the report below are potentially vulnerable to CVE-2018-3620 and CVE-2018-3646. Additionally the report displays if the asset is vulnerable to CVE-2018-3615 (GSX) or not. The report cross-references assets in your network with Intel's list of vulnerable processors.

Once you've identified possible vulnerabilities, we recommend following the following mitigation guides depending on your assets:
You can find a guide on how to add this report to your Lansweeper installation here.
Code:
Select Distinct Top 1000000 tblAssets.AssetID,
  tblAssets.AssetName,
  tblAssets.Domain,
  tblAssetCustom.Manufacturer,
  tblAssetCustom.Model,
  tblAssets.Processor As CPU,
  tsysAssetTypes.AssetTypeIcon10 As icon,
  tblAssets.IPAddress,
  Case
    When (tblAssets.Processor Like '%E5-%' And (tblAssets.Processor Like '%v5%'
      Or tblAssets.Processor Like '%v6%')) Or
      ((tblAssets.Processor Like '%I3-6%' Or tblAssets.Processor Like '%I3-7%'
      Or tblAssets.Processor Like '%I3-8%') Or
      (tblAssets.Processor Like '%I5-6%' Or tblAssets.Processor Like '%I5-7%' Or
      tblAssets.Processor Like '%I5-8%') Or (tblAssets.Processor Like '%I7-6%'
      Or tblAssets.Processor Like '%I7-7%' Or tblAssets.Processor Like '%I7-8%')
      Or (tblAssets.Processor Like '%I9-6%' Or tblAssets.Processor Like '%I9-7%'
      Or tblAssets.Processor Like '%I9-8%')) Then 'Yes'
    Else 'No'
  End As [Potentially Vulnerable to SGX],
  tblAssets.Lastseen,
  tblAssets.Lasttried
From tblAssets
  Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
  Inner Join tsysAssetTypes On tsysAssetTypes.AssetType = tblAssets.Assettype
Where ((tblAssets.Processor Like '%I3-%' Or tblAssets.Processor Like '%I5-%' Or
      tblAssets.Processor Like '%I7-%' Or tblAssets.Processor Like '%I9-%') Or
    ((tblAssets.Processor Like '%34__%' Or tblAssets.Processor Like '%36__%' Or
        tblAssets.Processor Like '%55__%' Or tblAssets.Processor Like '%56__%'
        Or tblAssets.Processor Like '%65__%' Or tblAssets.Processor Like
        '%75__%' Or tblAssets.Processor Like '%E3-%' Or
        tblAssets.Processor Like '%E5-%' Or tblAssets.Processor Like '%E7-%' Or
        tblAssets.Processor Like '%D-21%' Or tblAssets.Processor Like '%D-15%')
      And tblAssets.Processor Like '%Xeon%') Or ((tblAssets.Processor Like
        '%Bronze%' Or tblAssets.Processor Like '%Silver%' Or
        tblAssets.Processor Like '%Gold%' Or tblAssets.Processor Like
        '%Platinum%'))) And tblAssetCustom.State = 1
Order By tblAssets.Domain,
  tblAssets.AssetName

Active Discussions

Lansweeper Wake on Lan Issues
by  miharix   Go to last post Go to first unread
Last post: Today at 6:23:13 PM(UTC)
Lansweeper Export Ticket List
by  Yassine Dakir  
Go to last post Go to first unread
Last post: Today at 12:29:07 PM(UTC)
Lansweeper AWS scanning appears to only cover 1 account
by  Vincent Pollock   Go to last post Go to first unread
Last post: Yesterday at 9:26:04 PM(UTC)
Lansweeper TCP 445 to external IP during LS scan?
by  jvogler  
Go to last post Go to first unread
Last post: Yesterday at 8:02:06 PM(UTC)
Lansweeper Use Wildcard for User Name in Allowed Administrator
by  FP  
Go to last post Go to first unread
Last post: 2/22/2021 10:33:25 PM(UTC)
Lansweeper Helpdesk report for tickets for all on one reason
by  TimHolmes1973   Go to last post Go to first unread
Last post: 2/22/2021 7:22:56 PM(UTC)
Lansweeper Issues Updating
by  FrankSc  
Go to last post Go to first unread
Last post: 2/22/2021 11:06:50 AM(UTC)