• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

ETH Zurich Researchers Discover New Security Vulnerability in Intel Processors

Nomad76

News Editor
Staff member
Joined
May 21, 2024
Messages
1,282 (3.57/day)
Computer scientists at ETH Zurich discover new class of vulnerabilities in Intel processors, allowing them to break down barriers between different users of a processor using carefully crafted instruction sequences. Entire processor memory can be read by employing quick, repeated attacks. Anyone who speculates on likely events ahead of time and prepares accordingly can react quicker to new developments. What practically every person does every day, consciously or unconsciously, is also used by modern computer processors to speed up the execution of programs. They have so-called speculative technologies which allow them to execute instructions on reserve that experience suggests are likely to come next. Anticipating individual computing steps accelerates the overall processing of information.

However, what boosts computer performance in normal operation can also open up a backdoor for hackers, as recent research by computer scientists from the Computer Security Group (COMSEC) at the Department of Information Technology and Electrical Engineering at ETH Zurich shows. The computer scientists have discovered a new class of vulnerabilities that can be exploited to misuse the prediction calculations of the CPU (central processing unit) in order to gain unauthorized access to information from other processor users.



Update:: Intel released a security advisory regarding CVE-2024-45332, accompanied by a public announcement, and provided TechPowerUp with the following statement:

"We appreciate the work done by ETH Zurich on this research and collaboration on coordinated public disclosure. Intel is strengthening its Spectre v2 hardware mitigations and recommends customers contact their system manufacturer for the appropriate update. To date, Intel is not aware of any real-world exploits of transient execution vulnerabilities.", Intel spokesperson


PC, laptop and server processors all affected
"The security vulnerability affects all Intel processors," emphasises Kaveh Razavi, head of COMSEC. "We can use the vulnerability to read the entire contents of the processor's buffer memory (cache) and the working memory (RAM) of another user of the same CPU." The CPU uses the RAM (random access memory) and cache to temporarily store calculation steps and information that is likely to be needed next.

This vulnerability fundamentally undermines data security, particularly in the cloud environment where many users share the same hardware resources. It affects the processors of the world's largest CPU manufacturer, which are used in PCs and laptops, as well as those used in data center servers.

Nanosecond gap in authority check
The so-called BPRC (Branch Predictor Race Conditions) emerge during a brief period of a few nanoseconds when the processor switches between prediction calculations for two users with different permissions, explains Sandro Rüegge, who has been examining the vulnerability in detail over the past few months.

Breaking through the built-in protective barriers between users, known as privileges, is possible because the permissions for individual activities are not stored at the same time as the calculations. With special inputs, it is now possible to cause ambiguity in the sequence of events when changing users, resulting in incorrect assignment of privileges. An attacker could exploit this in order to read an information byte (a unit consisting of eight binary 0/1 pieces of information).

Unlocking entire contents of memory byte by byte
The disclosure of a single byte would be negligible. However, the attack can be repeated in quick succession, allowing the contents of the entire memory to be read over time, explains Rüegge. "We can trigger the error repeatedly and achieve a readout speed of over 5000 bytes per second." In the event of an attack, therefore, it is only a matter of time before the information in the entire CPU memory falls into the wrong hands.

Part of a series of security vulnerabilities
The vulnerability that the ETH Zurich researchers have now identified is not the first to be discovered in the speculative CPU technologies introduced in the mid-1990s. In 2017, Spectre and Meltdown were the first two vulnerabilities of this kind to hit the headlines, and new variants have been appearing regularly ever since. Johannes Wikner, a former PhD student in Razavi's group, already identified a vulnerability known as Retbleed back in 2022. He exploited traces of speculatively executed instructions in the CPU's cache to access information from other users.

Suspicious signal reveals vulnerability
The starting point for the discovery of the new vulnerability class was work that followed on from the Retbleed investigations. "I examined the functions of the protective measures that Intel had introduced to patch up the Retbleed vulnerability," says Johannes Wikner.

In doing so, he discovered an unusual signal from the cache memory that appeared regardless of whether the protective measures were enabled or disabled. Rüegge then took over detailed analysis of the cause of the signal and, based on this work, was able to uncover the new attack vector.

Fundamental architectural problem
The vulnerability was discovered back in September 2024. Since then, Intel has implemented protective measures to secure its processors. Nevertheless, there are many indications that the problem is more serious. "The series of newly discovered vulnerabilities in speculative technologies is an indication of fundamental flaws in the architecture," Razavi points out. "The gaps have to be found one by one and then closed."

Closing these sorts of gaps requires a special update to the processor's microcode. This can be done via a BIOS or operating system update and should therefore be installed on our PCs in one of the latest cumulative updates from Windows.

View at TechPowerUp Main Site | Source
 
"exploited to misuse the prediction calculations" That is why Intel rid prefect, hyper threading.

AMD employs predictive calculations in various aspects of its technology, in its processors and GPUs, AMD integrates machine learning and predictive algorithms to optimize performance, enhance efficiency, and anticipate workloads. Additionally, AMD's AI accelerators leverage predictive modeling to improve data processing and deep learning tasks.

The fact is, any predictive process method can be used in a nefarious way.
 
I think people with education know about si prefixes?

like kilo, like in a thousands of meters = kilometer
or kilo in gramm like a thousands of gramm

Stupid people say stupid things. Especially in the sense of over ... Why not say more than 5Kibibytes per seconds?
... 5000 bytes per second.

Well: How long will it take until someone claims, that security issue will not matter?

I miss the following informations

which CVE number? Which CVE link?

Is it already fixed?

A year without any action. Count in the holiday season, ...
The vulnerability was discovered back in September 2024.

I'm so happy gnu linux, FREE-BSD and the ohters are not affected

This can be done via a BIOS or operating system update and should therefore be installed on our PCs in one of the latest cumulative updates from Windows.

I'm so happy that early microcode loading is not necessary from "any" operating system.
edit: * when windows update works * broken for weeks on my recently purchased refurbished windows 11 pro 24h2 with official microsoft windows refurbisher license.
 
@_roman_ https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01247.html

Screenshot 2025-05-13 at 21-43-15 INTEL-SA-01247.png


Intel recommends that users of affected Intel® Processors update to the latest version provided by the system manufacturer that addresses these issues.
 
Last edited:
Quick, you need to throw out all your old Intel chips and buy new ones ? Right.

No ones out here buying Intel chips so don't worry.
 
This sounds like an actual hw bug, and not just some side channel attack.
 
Quick, you need to throw out all your old Intel chips and buy new ones ? Right.
No one who actually reads the story would, for their personal PCs. "We can use the vulnerability to read the entire contents of the processor's buffer memory (cache) and the working memory (RAM) of another user of the same CPU." So either physical access or running some type of malware is required...turns out all malware can do bad things. Just be careful with what you run on your PC, as has been the case forever.
 
This is not the only Intel vulnerability that was revealed this security cycle. The other is "Training Solo" discovered by VUSec. It affects multiple generations of Intel CPUs including latest Lunar and Arrow Lake, as well as certain ARM cores. AMD does not seem to be affected.
OS fixes (already applied to Linux) and microcode updates are required.

Edit: Both vulnerabilities seem to have a performance impact, for ETH Zurich one:
Our performance evaluation shows up to 2.7% overhead for the microcode mitigation on Alder Lake. We have also evaluated several potential alternative mitigation strategies in software with overheads between 1.6% (Coffee Lake Refresh) and 8.3% (Rocket lake).
For Training Solo I expect some overhead as well since mitigation includes fencing and thunking as only upper half of a cache line is considered safe.
 
Last edited:
In doing so, he discovered an unusual signal from the cache memory that appeared regardless of whether the protective measures were enabled or disabled.

Makes one wonder how much of those bugs are intentional. There's an actual true story of Swiss encoding machine, which had buitin possibility to read secure messages with great possibility of success. Sold all around the world.
 
Attempts to identify numerous errata and vulnerabilities may actually be larger vulnerabilities.
 
Planned obsolescence tactic. Say the older stuff is vulnerable to something so more ppl have to replace stuff since the "patch" gimps performance all the time and never seems to not.
 
Back
Top