Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Saturday November 03 2018, @05:48PM   Printer-friendly
from the hyperthreading-not-worth-the-hype? dept.

Researchers Exploit Another Intel Hyper-Threading Flaw

Five academics from the Tampere University of Technology in Finland and Technical University of Havana, Cuba, have discovered yet another flaw in Intel's Hyper-Threading (HT) technology that attackers could use to steal users' encrypted data, as reported by ZDNet today.

Other CPUs that use Simultaneous Multithreading (SMT) technology may also be affected by the bug, but so far only Intel's HT has been confirmed as vulnerable. SMT and HT are technologies that allow two or multiple computing threads to be executed on the same CPU core. Intel enables two threads per physical core with its HT technology.

[...] The vulnerability, which the researchers nicknamed PortSmash, allows attackers to create a malicious process that can run alongside another legitimate process using HT's parallel thread running capabilities. This malicious process can then leak information about the legitimate process and allow the attacker to reconstruct the encrypted data processed inside the legitimate process.

The researchers also made available the proof of concept (PoC) for the attack, showing that it is indeed feasible and not just theoretical. This PoC can now also be re-purposed and modified by attackers to launch a real attack against owners of systems using Intel CPUs.

Also at Ars Technica and The Register.

Related: OpenBSD disables Intel's hyper-threading over CPU data leak fears
TLBleed Affects Intel Processors with Hyperthreading to Leak Encryption Keys, Non-Trivial to Exploit
OpenBSD Chief De Raadt Says No Easy Fix For New Intel CPU Bug
Intel 'Gags' Linux Distros From Revealing Performance Hit From Spectre Patches


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Informative) by Anonymous Coward on Sunday November 04 2018, @08:25PM

    by Anonymous Coward on Sunday November 04 2018, @08:25PM (#757715)

    What happened was that:

    A) Motorola could not scale their cores as well as Intel could.

    B) People stopped programming in machine code.

    All this made the x86 that much more acceptable.

    Never mind that Microsoft convinced Intel to maintain backwards compatibility even as x86 went from 16 bit to 32 bit.

    This meant that people could run the same software on a modern Windows install as on a old DOS one. Leading to quite the captive audience.

    By comparison the original 68k didn't have a MMU (nor did the 8086, but that is a sidetrack). And when later ones introduced one, it broke compatibility with older 68ks.

    Starting Score:    0  points
    Moderation   +2  
       Informative=2, Total=2
    Extra 'Informative' Modifier   0  

    Total Score:   2