After Spectre and Meltdown.. Now “Foreshadow” secruity CB HOLE! ONLY INTEL! Dump Intel buy AMD! Videos!

[motormafia]

https://www.hackread.com/intel-chip-flaw-foreshadow-attacks-sgx-tech-to-extract-data/

New Intel chip flaw “Foreshadow” attacks SGX technology to extract sensitive data
August 15th, 2018 Waqas Security 0 comments
by Waqas
on August 15th, 2018

TagsCPU, Intel, internet, Malware, security, Spectre, Technology, Vulnerability
Share on FacebookShare on Twitter

Security fraternity is still dealing with the adverse consequences and versatile range of threats caused by the Spectre and Meltdown vulnerabilities. But, to add to their misery, there is another possibly worst hardware flaw detected by security researchers in Intel chips. This flaw, dubbed as Foreshadow, can obtain information even from the most secured components of the CPU. The flaw is identified by security experts from five different, credible institutions.
Foreshadow is quite similar to the Spectre vulnerability; it can be detrimental to the SGX (Software Guard Extensions) elements of the Intel chips. It must be noted that SGX is amongst the most secure elements of Intel chips that lets programs set up enclaves, which are the processor’s protected areas. These areas are responsible for handling sensitive data and are restricted just like the sandbox. This means a code cannot be executed from within them. When malware or virus infects the device, the data present in these enclaves remains protected. Foreshadow can bypass the security of these enclaves.

There are two versions of Foreshadow; one is the original attack [PDF] that can extract data from the enclaves. The other is called Foreshadow NG (Next Generation) [PDF], which can extract information from the L1 cache. It can potentially affect virtual machines, OS kernel memory, hypervisors, and system management mode memory. In fact, it has the capability of threatening the overall infrastructure of the Cloud platform.
According to Yuval Yarom, microarchitecture security researcher, there are some surprising aspects of this discovery such as it can obtain extensive information from SGX. SGX technology, found in Skylake and Kaby Lake processors from Intel, stores critically sensitive data including credit card information or social security number. Speculative Execution is the process that breaks down this information. It is basically a performance-boosting feature that is present in a majority of computer chips. But, if it gets engineered through malware, it is easily possible to extract sensitive data from the securest components of the PC.
SGX technology is installed in Intel chips to prevent speculative execution led attacks. But, researchers claim that by creating a “shadow copy” of any SGX enclave at an unprotected location of the CPU can lead to bypassing the security features. This would allow an attacker to read protected data and all protective measures will become useless.
However, accomplishing this feat isn’t too easy as was the case with other hardware flaws like Spectre and Meltdown. So far, security researchers haven’t identified any attacks that exploit these flaws or even the newly identified Foreshadow. Since it isn’t an easy exploit to carry out, so, hackers would most likely want to stick to other, easy-to-achieve hacking methods like email phishing.
Yet, Foreshadow is a concerning flaw because it can be leveraged to target data centers and compromise the security mechanisms implemented between two or more virtual machines. Cloud service can also be exploited to read memory from different users hosted on a single server.

The good news is that on Tuesday Intel will be releasing new patches to address Foreshadow vulnerability and Microsoft also will be releasing fixes. The new fixes will work with previously released updates for Spectre and Meltdown flaws.
According to Jeff Ready, CEO of Scale Computing “The design flaw in Intel chips have left windows and Linux systems vulnerable. Any device or services connected to the chips is essentially left at risk – especially after the latest flaw that was revealed – Foreshadow. The main focus is working in real time to identify the issues and look at what needs to be patched. Performance impacts will be seen across the industry.”
Systems that utilize software-defined storage via a mid-layer filesystem will likely experience the most impact. Many software-defined storage solutions, which use a mid-layer filesystem will likely have a much larger performance impact as a result of these fixes. After the patches and fixes roll out, we will be able to see the true extent of the impact.”








https://securitybrief.asia/story/flaw-discovered-intel-chips-allows-attackers-steal-cloud-data/

Intel-Core-S-series-Chip.jpg
Tags

Security vulnerabilities, Spectre, Foreshadow, CPU, RedLock, Intel, Meltdown
Flaw discovered in Intel chips, allows attackers to steal cloud data
Lew Kai Ping
Lew Kai Ping
August 16, 2018

Researchers have discovered another security flaw in Intel security chips – the third one this year after Spectre and Meltdown.

The flaw allows an attacker to steal sensitive information stored on personal computers or third-party clouds.

According to their research report, Foreshadow has two versions, the original attack designed to extract data from Intel SGX enclaves and a Next-Generation version which affects Virtual Machines (VMs), hypervisors (VMM), operating system (OS) kernel memory, and System Management Mode (SMM) memory.

The flaw was discovered by researchers from the Israel Institute of Technology, University of Michigan, the University of Adelaide, and the Catholic University of Leuven.

The report says that mitigations against Meltdown and Spectre are not effective against Foreshadow and Foreshadow-NG.

On its website, Intel says it has “worked with operating system vendors, equipment manufacturers, and other ecosystem partners to develop platform firmware and software updates that can help protect systems from these methods.”

“This includes the release of updated Intel microprocessor microcode to our customers and partners.”
Affected CPUs

Intel confirmed that Foreshadow affects all SGX-enabled Core processors (Skylake and Kaby Lake), while Atom family processors with SGX support remain unaffected. Intel confirmed that Foreshadow-NG affects the following processes:

· Intel Core i3/i5/i7/M processor (45nm and 32nm)

· 2nd/3rd/4th/5th/6th/7th/8th generation Intel Core processors

· Intel Core X-series Processor Family for Intel X99 and X299 platforms

· Intel Xeon processor 3400/3600/5500/5600/6500/7500 series

· Intel Xeon Processor E3 v1/v2/v3/v4/v5/v6 Family

· Intel® Xeon Processor E5 v1/v2/v3/v4 Family

· Intel® Xeon Processor E7 v1/v2/v3/v4 Family

· Intel® Xeon Processor Scalable Family

· Intel® Xeon Processor D (1500, 2100)

Cloud threat defence company RedLock’s Cloud Security VP Matthew Chiodi says, “What’s interesting about the Intel disclosure is that researchers simply followed the thread left by Spectre and Meltdown—this isn’t a completely new class of vulnerabilities.

“This means that while Intel is not officially aware of any exploits that take advantage of this today, certainly advanced nation-states have been working on them.

“Interestingly enough, back in June, the OpenBSD project announced plans to disable support for Intel CPU hyper-threading (HT) due to security concerns around more ‘Spectre-class bugs’ - Their announcement has proved prescient.”

Chiodi adds that public cloud titans Google, Microsoft and AWS quickly responded to Foreshadow by updating their respective infrastructure and services.

“Enterprise cloud consumers tangibly benefited as the vast majority of them are not operating multi-tenant workloads on the same VM.

“That doesn’t mean there’s nothing to do on the end-user side, but the cloud providers have already done a lot of the heavy lifting.

He concludes,” The bottom line is that even the best and fastest fixes aren’t effective unless all stakeholders do their part—this is especially relevant in public cloud given the shared responsibility model.

"It only takes one party, one weak link in the chain, for the exposure to remain.”

 

[eatshitndie]

what about its forebear “foreplay”?

 

[tun_dr_m]

I will not be surprised when the thieves took all the money in the world from banks. Everyone else goes broke.

 

[motormafia]

https://www.extremetech.com/computing/275456-intel-foreshadow-bug-break-4k-hardware-drm


Could the Intel Foreshadow Bug Break 4K Hardware DRM? [Updated]

• By Joel Hruska on August 16, 2018 at 11:02 am
• 4 Comments

• Facebook
• Twitter
• Google Plus
• Reddit
• Hacker News

Update: We’ve heard from Intel on this issue. A company spokesperson states: “Mitigations that address this [the L1 Terminal Fault bug, aka Foreshadow] have already been made available – which also address the attestation scenario. The best thing for people to do is simply to keep their systems up to date. Once systems are updated, we expect the risk to most consumers and enterprise users will be low.”
Original Story Below:
Earlier this week, news broke that a set of three vulnerabilities — collectively referred to as Foreshadow — have been found in Intel microprocessors. These vulnerabilities specifically impact Intel’s implementation of a security feature known as Software Guard Extensions, a technology Intel developed to run hardened, protected code even in cases where the underlying operating system or hardware might not be secure. But just how far does the flaw extend, and what kind of practical use can it be put to?
The Register recently spoke to one of the flaw’s discoverers, Dr. Yuval Yarom, who minced no words in his evaluation. One of the hallmarks of Foreshadow is that it can be used to falsify attestation information, which is to say, SGX can appear to attest that code is valid and unchanged while said code is anything but. Without the ability to verify that the code in question is actually the code that’s running, Dr. Yarom says, “The whole trust model collapses.”
“The main promise of SGX is that you can write code, and ship it to someone you do not fully trust,” Dr. Yarom told the Register. “That person will run the code inside SGX on their machine, and you can see that whatever they run there is protected, because you know… they haven’t modified your code, they haven’t accessed the data that your code used.”
One specific example Yarom gave of an example application that could be harmed by this flaw is a video player that used SGX to implement its DRM mechanism. The player obviously isn’t intended to allow for the video stream to be copied, but if you can muck with the SGX attestation, you can alter the player to claim that its stream is properly protected when it isn’t. In theory, this sounds like precisely the kind of break that PC pirates might exploit to break Microsoft’s PlayReady 3.0, the 4K content protection that (still) makes Netflix playback require a lot of jumping through hoops, including the use of specific browsers (Microsoft Edge) and compatible hardware (recent AMD APUs, or Kaby Lake-and-later CPUs). But it’s not at all clear if this flaw will actually enable that kind of activity. Intel’s documentation makes it absolutely clear that SGX can be used for DRM, but it’s not evident that PlayReady 3.0 actually uses it.
Microsoft’s publicly available documentation is filled with references to Trusted Execution Environments (TEEs) and the need to have hardware DRM protection baked in at the physical level in order to certify a device for SL3000 feature levels (and that’s the relevant target, as near as I can tell). Older levels, like SL2000, are software based.

SGX was technically introduced with Skylake, not Kaby Lake, and Netflix 4K playback requires the latter. This could be read to imply that whatever DRM solution MS relies on, it isn’t explicitly tied to SGX. On the other hand, however, other reports have suggested that while Skylake CPUs deployed SGX, the firmware and software that shipped with Skylake systems wasn’t necessarily capable of enabling the feature. If Intel made supporting the full capabilities of SGX out of the box mandatory only with Kaby Lake it might explain why Microsoft didn’t support the feature until 7th Generation CPUs.
On the other hand, we know that Nvidia and AMD have both added support for 4K playback over both CPUs and GPUs, which strongly implies that Microsoft’s Trusted Execution Environments are designed to be flexible rather than demanding only one vendor’s hardware implementation. And given that Intel is already distributing microcode updates to fix this bug (or at least, major parts of it), it’s not clear if there’s a meaningful risk in the first place. The window of opportunity for attacks like this to impact mainstream video streaming services could ultimately be small to nonexistent. Like Meltdown and Spectre, this bug isn’t going to principally hit consumers but cloud service providers and enterprises. So far, Intel’s data center revenue has weathered this barrage of bad news unscathed — there are some who think the problems have created opportunities for future Intel products and accelerated upgrade cycles.
Now Read: New Speculative Execution Security Flaw Cracks Intel’s Software Guard Extensions, 4K Netflix is finally coming to PCs, but you probably still can’t watch it, and Windows 10’s PlayReady 3.0 mandates hardware DRM for 4K playback




https://www.technologyreview.com/th...laws-are-the-latest-sign-of-the-chipocalypse/

The Download
What's up in emerging technology

August 14, 2018

Intel’s “Foreshadow” flaws are the latest sign of the chipocalypse


The vulnerabilities could allow hackers to gain access to sensitive data in a computer’s memory

The bad news: According to a report in ZDNet, the flaws, which Intel calls “L1 Terminal Fault” and researchers have grouped under the moniker “Foreshadow,” are similar in nature to the Spectre and Meltdown security holes that were uncovered earlier this year in billions of chips from both Intel and AMD. AMD says its products aren’t vulnerable to the Foreshadow flaws, so this time it’s only Intel’s central processing unit chips that appear to be affected.

The downside: Foreshadow could let hackers mount “side channel” attacks that give them access to the portion of a chip’s core memory that holds things like passwords and encryption keys. Machines running in the computing cloud and handling workloads for lots of different customers could be particularly vulnerable to such attacks.

The (slightly) better news: The researchers who found the security holes gave Intel a heads-up months ago, so it has had time to prepare software patches to minimize the risk. With both Spectre and Meltdown, Intel had to scramble to take corrective action. Cloud computing vendors like Microsoft and Amazon have also been issuing notices about steps they’ve taken to minimize the threat Foreshadow poses to customers.

A lingering risk: Because Foreshadow, Spectre, and Meltdown are all hardware-based flaws, there’s no guaranteed fix short of swapping out the chips. But security experts say the weaknesses are incredibly hard to exploit and that there’s no evidence so far to suggest this year’s chipocalypse has led to a hacking spree. Still, if your computer offers you an urgent software upgrade, be sure to take it immediately.


Image credit:

• Stratman2 | Flickr

https://www.theregister.co.uk/2018/08/15/foreshadow_sgx_software_attestations_collateral_damage/



Security


Foreshadow and Intel SGX software attestation: 'The whole trust model collapses'
El Reg talks to Dr Yuval Yarom about Intel's memory leaking catastrophe

By Richard Chirgwin 15 Aug 2018 at 09:42

28 SHARE ▼

Interview In the wake of yet another collection of Intel bugs, The Register had the chance to speak to Foreshadow co-discoverer and University of Adelaide and Data61 researcher Dr Yuval Yarom about its impact.

The main promise of SGX is that you can write code, and ship it to someone you do not fully trust. That person will run the code inside SGX on their machine, and you can see [it]...​

Dr Yarom explained that one of the big impacts of Foreshadow is that it destroys an important trust model – SGX attestations, which guarantee that the code you publish is the code someone else is running.

Think of it as tamper-evident packaging for software: having published your software, the SGX remote attestation will fail if someone changes it. If things are working properly, you only know a remote machine has signed the software – not whose machine it was.

If a Foreshadow (CVE-2018-3615) exploit were successful, it could break both the attestation and the privacy model.

Three more data-leaking security holes found in Intel chips as designers swap security for speed
READ MORE

Dr Yarom told us: “The main promise of SGX is that you can write code, and ship it to someone you do not fully trust. That person will run the code inside SGX on their machine, and you can see that whatever they run there is protected, because you know… they haven't modified your code, they haven't accessed the data that your code used.”

Someone writing a video player, he said, could use this as a rights protection mechanism: the player doesn't allow copying, and the publisher knows it's behaving correctly, because they're receiving the signed SGX attestation saying so.

“As part of our attack, what we managed to do is get the attestation keys.

“We can take your code, analyse it to see what it does, know how it should behave, change that behaviour – but we can fake the attestation,” he said – the code they run as attackers doesn't match the publisher's code, but the "tampered" code passes all the validity checks.

In the video player example, the attacker can change the code so it creates a copy of content, but still “allow it to attest to vendor of the software that it is still running, protected.”

"The whole trust model collapses," Dr Yarom told us.

In a press release from CSIRO/Data61, Dr Yarom said: "Intel will need to revoke the encryption keys used for authentication in millions of computers worldwide to mitigate the impact of Foreshadow."

As we observed reporting the vulnerability exploited by Foreshadow (and the other two vulnerabilities* that Intel discovered while investigating fixes), Intel created the exposure by prioritising performance over security, and Dr Yarom agreed.

“It's clear that Intel's recent design decisions focussed on how to optimise processors ... so that typical programs execute faster.

"What we now see is that these optimisations, particularly when we don't understand them, come at the cost of information about what the program is doing.”

He added that such decision-making isn't confined to Intel.

Dr Yarom said Intel's black-box approach to processors is the reason Data61 is putting its weight behind the RISC Foundation's open hardware efforts.

"It's about getting to know what's inside a processor, and getting to be able to make a guarantee of the behaviour of the processor.

"We need to make sure that these sorts of attacks aren't feasible, and for that we need the ability to reason about the behaviour of the processor," he said.

We need to make sure that these sorts of attacks aren't feasible, and for that we need the ability to reason about the behaviour of the processor​

Dr Yarom was part of one of two teams who independently discovered Foreshadow, working with Marina Minkin and Mark Silberstein of Technion; Ofir Weisse, Daniel Genkin, Baris Kasikci, and Thomas Wenisch of the University of Michigan.

A team from the imec-DistriNet research group at the KU Leuven – Jo Van Bulck, Frank Piessens, and Raoul Strackx – made the same discovery independently.

Dr Yarom explained that after Meltdown and Spectre landed in January, it was clear to researchers that SGX was a logical next vector to attack.

"Marina [Minkin] had worked with SGX, we talked about it a bit, and she mentioned a scenario which in SGX caused an access violation exception, instead of falling into 'abort page semantics'. Because Meltdown is related to access violation exceptions we decided to give it a try."

Once you know where to look for a vulnerability, he said, "most of the hard part is done". ®

* The researchers have called two related vulns – CVE-2018-3620 and CVE-2018-3646 – "Foreshadow-NG" (next generation). Intel refers to the three flaws collectively as "L1 terminal fault".

Yarom and the rest of the team are presenting "Foreshadow: Extracting the Keys to the Intel SGX Kingdom with Transient Out-of-Order Execution" on 16 August at the Usenix Security conference.

Tips and corrections

28 Comments

Sign up to our NewsletterGet IT in your inbox daily

• MORE
• Intel

 

[motormafia]

https://thehackernews.com/2018/08/foreshadow-intel-processor-vulnerability.html



Foreshadow Attacks — 3 New Intel CPU Side-Channel Flaws Discovered



August 14, 2018Swati Khandelwal

2018 has been quite a tough year for Intel.

While the chip-maker giant is still dealing with Meltdown and Spectre processor vulnerabilities, yet another major speculative execution flaw has been revealed in Intel's Core and Xeon lines of processors that may leave users vulnerable to cyber-attacks.

Dubbed Foreshadow, alternatively called L1 Terminal Fault or L1TF, the new attacks include three new speculative execution side-channel vulnerabilities affecting Intel processors.

The Foreshadow attacks could allow a hacker or malicious application to gain access to the sensitive data stored in a computer's memory or third-party clouds, including files, encryption keys, pictures, or passwords.

The three Foreshadow vulnerabilities have been categorized into two variants:

1.) Foreshadow

Foreshadow (PDF) targets a new technology originally been designed to protect select code and users' data from disclosure or modification, even if the entire system falls under attack:

• Intel Software Guard Extensions (SGX) — CVE-2018-3615

The new attack against SGX enclaves, which is resilient to Meltdown and Spectre attacks, may allow an unauthorized attacker to steal information residing in the L1 data cache—a protected portion of a chip's core memory that holds things like passwords and encryption keys—via side-channel analysis.

"Foreshadow enables an attacker to extract SGX sealing keys, previously sealed data can be modified and re-sealed," the researchers said. "With the extracted sealing key, an attacker can trivially calculate a valid Message Authentication Code (MAC), thus depriving the data owner from the ability to detect the modification."​

2.) Foreshadow: Next Generation (NG)

The second variant (PDF) includes two vulnerabilities, which target virtualization environments being used by large cloud computing providers like Amazon and Microsoft:

• Operating systems and System Management Mode (SMM) — CVE-2018-3620
• Virtualization software and Virtual Machine Monitors (VMM) — CVE-2018-3646

These flaws also disclose sensitive information residing in the L1 data cache, including the information stored in other virtual machines running on the same third-party cloud, with local user access or guest OS privilege via a terminal page fault and side-channel analysis.

"Using Foreshadow-NG, a malicious program running on the computer might be able to read some parts of the kernel's data," the researchers said. "As the kernel has access to data stored by other programs, a malicious program might be able to exploit Foreshadow-NG to access data belonging to other programs."​

Intel and Partners Releases Patches for Foreshadow Flaws

Since the mitigations available for Meltdown and Spectre are not sufficient to patch above mentioned-Foreshadow vulnerabilities, Intel and partners need to roll out new security patches at both software and microcode level.

"Foreshadow is different from Meltdown as it targets virtual machines and SGX in addition to data stored in the operating system's kernel (which was targeted by Meltdown)," the researchers said.​

You can see video demonstrations illustrating the Foreshadow vulnerabilities as well.




Since SGX is only supported in Intel processors, the Foreshadow bugs only affect Intel processors, though researchers have yet to test Foreshadow against ARM and AMD processors.

According to Intel, none of these attacks so far appear to have been seen in the wild, and the company has started releasing patches for all the new speculative execution flaws. You can check the status of the security patches here.

Besides Intel, Microsoft and Oracle on Tuesday also released security advisories and updates for L1TF. Cloud services like Microsoft Azure, Amazon Web Services, and Google Compute Engine have already mitigated the issue.

Foreshadow bug was discovered by two teams of researchers—researchers from imec-DistriNet and KU Leuven; and researchers from Technion, University of Michigan, the University of Adelaide and CSIRO's Data61.

Have something to say about this article? Comment below or share it with us on Facebook, Twitter or our LinkedIn Group.

 

[motormafia]

 

[motormafia]

 

[Leongsam]

what about its forebear “foreplay”?

It was left in the operating room along with foreskin.

 

[motormafia]

Intel CPU 多年来一直玩取巧欺骗的阴招, HYPER-THREADING, 把每一个计算机芯变身欺骗成两个分身, 看起来有两个,实际上里面只有一个而已. 这样子全部欺骗成双倍,8个芯被以为是16个. 让操作系统因为处理器非常强大,同时可以启动很多程式共享,事实上做不到. 现在因此出现了很大的安全隐患,这只发生在INTEL 而不发生在AMD. 因为AMD不玩这阴招. 原来,假的分身两个共享一块L1高速内存,因为本来就没有两套,实际上只有一套. 这样子就泄露了机密.因为共享的L1高速内存里面,就有另一个分身才应该看到的机密资料,因为共享而被泄露. 就像共享浴室看到别人洗澡了! 补救的代价就是系统变成更慢! 每次共享要清除内存! 浪费时间得不偿失! https://www.sammyboy.com/threads/after-spectre-and-meltdown-now-“foreshadow”-secruity-cb-hole-only-intel-dump-intel-buy-amd-videos.257881/


Intel CPU has been playing tricks of deception for many years, HYPER-THREADING, deceiving each computer core into two avatars, it seems that there are two, in fact there is only one inside. This is all deceived into double, 8 cores are thought to be 16. Let the operating system because the processor is very powerful, and can start a lot of program sharing, in fact can not do. Now there is a big security risk, this only happens in INTEL and does not happen in AMD. Because AMD does not play this trick. Originally, the fake split two shared a L1 high-speed memory, because there are no two sets, there is actually only one set. This reveals the secret. Because of the shared L1 high-speed memory inside There is another confidential information that should be seen in the avatar, because it is shared and leaked. Just like the shared bathroom sees someone else taking a shower! The price of the remedy is that the system becomes slower! Every time you share, you need to flush the memory! Wasting time is not worth the loss. !

 

[eatshitndie]

It was left in the operating room along with foreskin.

and later it morphs to foregone, forget, forgive, forever.

 

[Tony Tan]

It is about time for the Chinese to enter the business of CPU & GPU, break the Chow Ang Moh Monopoly and Cannibalize the Silicon Valley. There is sufficient domestic market & market that are against the USA, the situation of CPU & GPU today is such that:

FOR A HUGE MAJORITY PURPOSES, the existing CPUs & GPUs are OVERKILL - too powerful, unnecessarily powerful. That means you DON'T need to compete by performance, DON'T need top performance to win. You can win by RELIABILITY, SECURITY, AFFORDABLE ALTERNATIVES, TRUSTED & POLITICALLY AFFILIATED.

It is already too obvious that you can not trust Ang Moh products. You don't need every computer to be supercomputer. Any way, the real good supercomputers are also using Chinese own CPUs not the Ang Moh CPUs any longer. So China should commercialize their military CPUs, grow businesses in this area, ban Ang Moh products.

 

[halsey02]

What happened to the DATA stolen, of the Stinkhealh medical records, which included Mee Siam Mai Hum & Wooden? so far, no picture, no sound?. Did they pay the hackers for the datas??