Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

New Speculative Execution Vulnerability Gives CISOs a New Reason to Lose Sleep

The vulnerability, dubbed SWAPGS, is an undetectable threat to data security, similar in some respects to Spectre and Meltdown.

Bogdan Botezatu, director of threat research at BitDefender, leans across the table in a hotel lobby coffee shop to make his point. "When you're a CISO, there is no single of vulnerability you're aware of that doesn't keep you awake at night." The new vulnerability his team of researchers found — the vulnerability they will reveal in a press conference this evening — is one that he says should definitely contribute to CISO insomnia.

The new vulnerability, dubbed SWAPGS by the BitDefender research team, is a speculative execution vulnerability that Botezatu says is similar in some respects to Spectre and Meltdown. "What we have done is to manipulate this instruction called SWAPGS in order to sample information from the realm of the operating system memory into the user space," he explains.

SWAPGS is an instruction that swaps the contents of a particular register with the contents of a specific memory location. The instruction is defined as a privileged instruction that should be available only to system software, such as a hypervisor. One of the things that makes the instruction dangerous when exploited is that it can provide rapid access to certain data structures used by the operating system kernel.

When the instruction is manipulated, Botezatu says, "This can lead to all sorts of trouble like leaking out information about passwords, encryption, keys, tokens, authentication, cookies, and other sensitive information that goes through the processor."

Like many of the other speculative execution exploits that have been found, SWAPGS doesn't allow the attacker to manipulate the data being stored in the memory location — it only allows for the contents of that memory location to be monitored. "You just poke the memory, and run a time-based attack. If it's something interesting, it's fine. If not, you have just lost 20 seconds and you need to go back to square one," Botezatu explains.

As with most of the other speculative execution attacks, Botezatu sees SWAPGS as something that could be a tool for patient nation-state actors, not finance-focused criminals. Criminal actors, he says, can simply launch repeated phishing attacks to get the information that might become available through SWAPGS.

Still, he points out, a speculative execution attack like SWAPGS is dangerous because it bypasses hardware-based protection and is undetectable by normal security packages. Furthermore, while BitDefender followed responsible disclosure and Microsoft has issued a Window patch for the vulnerability, Botezatu says, "We know that in enterprises, patch adoption is not something that happens overnight. That can take anywhere from one to 180 days, if you're lucky."

Related content:

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/10/2019 | 7:02:41 PM
Response from IBM X-Force Exchange

FreeBSD, when running on a 64bit system with a FreeBSD/amd64 kernel, could allow a local attacker to gain elevated privileges on the system. By causing a General Protection Fault while the kernel is returning from processing an interrupt or system call, a local attacker could cause the incorrect execution of swapgs CPU instruction. An attacker could exploit this vulnerability to execute arbitrary code on the system with kernel level privileges.

The SWAPGS Side-Channel Attack Against Windows
Researchers from Bitdefender have discovered a new side-channel attack they have named SWAPGS. While building on research from the previously discovered and widely publicized Spectre and Meltdown attacks, SWAPGS can reportedly bypass all known mitigations for them. SWAPGS is a variation on the Spectre Variant 1 vulnerability. The attack exploits the speculative execution of a specific instruction on Intel chips, combined with the use of the instruction by Windows operating systems inside a gadget. Exploitation requires an attacker being able to log on to a vulnerable system and could allow the attacker to obtain sensitive information from a system's memory which could include the likes of credentials and encryption keys or pointers and addresses that could potentially be used for privilege escalation attacks. The Intel CPU's affected are from the Ivy Bridge series on. Microsoft released an update to address the vulnerability (CVE-2019-1125) in its July bulletins and has issued further guidance which notes that a microcode update is not required to address the vulnerability

What I get from both findings is that the user has to login and then they have to verify if Speculative Execution is part of the "Ivy Bridge" processor. If it is, then that is where priviledge escalation could take place but there are a few things they must do first is identify if this is an "Ivy Bridge" processor.

  • Write-host "Check if Ivy Bridge Processor"
    Write-Host "-----------------------------"
    $type = (get-wmiobject -class Win32_processor).Name
    $type
    Write-Host ""
    Write-Host "Check Ivy Processor Status"
    Write-Host "--------------------------"
    $check = $type.substring(18,8).split("-")[1]
    $proc = $check.substring(0,2)
    $ivy = @("30","31","32","33","34","35","36","37")
    foreach ($i in $ivy) {
        if ($i -eq $proc) {
            Write-Host "Ivy Bridge Processor Identified: " $type
            exit
        } 
    } Write-Host "Ivy Bridge Processor not identified"
    

There is a much better way of checking for Ivy Bridge but this is good for right now, Speculative Processor check can be downloaded from the web to help with the identification, but this is a good start.


I am getting rusty in my Powershell programming, need to get back on it.


Todd
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Lessons from the NSA: Know Your Assets
Robert Lemos, Contributing Writer,  12/12/2019
4 Tips to Run Fast in the Face of Digital Transformation
Shane Buckley, President & Chief Operating Officer, Gigamon,  12/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19797
PUBLISHED: 2019-12-15
read_colordef in read.c in Xfig fig2dev 3.2.7b has an out-of-bounds write.
CVE-2019-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.