210

Intel breathes a sigh of relief as the spotlight moves off of them for a beat.

top 50 comments
sorted by: hot top controversial new old
[-] sxan@midwest.social 144 points 4 months ago

Except the AMD exploit requires ring 0 access and is almost irrelevant to most users, whereas the Intel issues are physically destroying people's computers. The scale of the issues are utterly incomparable.

I'm much more angry with whatever dipshit at AMD decided to revoke permission for ZLUDA, and that they haven't yet been fired.

[-] ngwoo@lemmy.world 15 points 4 months ago

People grant kernel access all the time without thinking. Video game anti-cheat is a good example. It's a pretty potent vector of attack since you can never trust these companies to keep themselves secure.

[-] helpmyusernamewontfi@lemmy.today 4 points 4 months ago

Apex Legends and Genshin Impact being a good example of this.

[-] Evilcoleslaw@lemmy.world 3 points 4 months ago

The Apex Legends hacking situation was unrelated to the anti-cheat despite initial reports. It didn't stop the hack but it also wasn't the vector for the attacks.

Genshin Impact's anti-cheat however was an unmitigated disaster.

[-] helpmyusernamewontfi@lemmy.today 3 points 4 months ago

The Apex Legends hacking situation was unrelated to the anti-cheat despite initial reports

you're right, thanks for the clarification! https://inv.tux.pizza/watch?v=lzW4SDm0yWM

[-] HandMadeArtisanRobot@lemmy.world 11 points 4 months ago
[-] sxan@midwest.social 1 points 4 months ago

Didn't the author confirm the takedown came from AMD and not NVidia? AMD isn't responsible for third party software running on their hardware.

Although, IIRC they either sanctioned it or provided some initial funding, which might have put them in a more culpable position. Still, I'm pretty sure the takedown came from AMD, and it doesn't make sense that they're doing NVidia's policing for then.

[-] Evilcoleslaw@lemmy.world 5 points 4 months ago

They were paying for its development for about a year and a half.

[-] sxan@midwest.social 1 points 4 months ago

Yeah, that'd do it. Although, again, it looks like the restriction wasn't in the NVIDIA licensing wording until recently. IANAL, but you it both parties are required to agree to contract changes; if AMD's contributions were all pre-wording change, they merely need to dust their hands; it's OSS. Why are they doing NVIDIA's dirty work for them?

I'm not convinced.

[-] 1984@lemmy.today 11 points 4 months ago

I'm thinking there are more things like this, and maybe even some are intentionally put in to please government actors. Intels management engine is like a small computer inside the computer, and amd has something simular. This computer can work completely independent of what the main computer does and has network access.

[-] ichbinjasokreativ@lemmy.world 18 points 4 months ago

Difference is that Intel's Management engine can be controlled via the network whereas AMD's platform security processor is local-only.

The much bigger problem is Microsoft's Pluton coprocessor, which they plan on making mandatory for using windows in the future.

[-] 1984@lemmy.today 5 points 4 months ago

I didn't know amd is local only, that's amazing. Another huge reason to go for amd.

And yeah, Pluton... I don't use windows anymore and I encourage everyone to switch to Linux. But only a few people care about their privacy and not being tracked.

[-] ichbinjasokreativ@lemmy.world 3 points 4 months ago* (last edited 4 months ago)

It used to be a major pro-AMD reason for me too, but it's become irrelevant since pluton. Weird thing is, pluton was announced with much fanfare for Ryzen 6000, but I've not heard about it since.

Edit: I just read up on this topic again and found out that both purism and system76 disable the Intel ME in all their products (don't know if all of it is disabled, since it normally controls a lot of necessary components)

Edit 2: they can either remove most of its code from the flash, or use a disabling system that Intel had literally developed for the NSA.

[-] Caboose12000@lemmy.world 3 points 4 months ago

what's ZLUDA? can you ELI5?

[-] Evilcoleslaw@lemmy.world 4 points 4 months ago

ZLUDA was an open source translation layer for CUDA. So basically developers could take code from projects written for Nvidia's CUDA and use ZLUDA to run them on other hardware. Originally the dev was focused on Intel but AMD started paying him and he focused on AMD hardware. They stopped funding him earlier in the year and now it appears AMD legal has gone back on their earlier permission for him to keep distributing the code.

load more comments (1 replies)
[-] breadsmasher@lemmy.world 86 points 4 months ago

This post was sponsored by INTEL™️

/jk

[-] Rooki@lemmy.world 88 points 4 months ago
[-] db2@lemmy.world 21 points 4 months ago

How long were you sitting on that one waiting for the perfect moment?

[-] SkaveRat@discuss.tchncs.de 6 points 4 months ago* (last edited 4 months ago)

Which is by pure chance also what the person said who got the exploit list from Intel

[-] altima_neo@lemmy.zip 16 points 4 months ago

Wouldnt be surprised if the researchers were Intel researchers.

[-] Railcar8095@lemm.ee 11 points 4 months ago

*100 employees were fired too allocate budget for this sponsorship

[-] j4k3@lemmy.world 81 points 4 months ago

Funny. No. This is not remotely comparable to CPU's crashing because of a lack of R&D and half ass quarter earnings profiteering culture's lack of intelligent long term thinking. It is not remote accessible. This is just corporate psyops in an attempt to coverup their overwhelming neo feudal incompetence. If they had the staff and invested reasonably, the problems wouldn't happen. Paint the world in shit to continue the claim that yours does not stink. Only idiots buy into that.

[-] bruhduh@lemmy.world 60 points 4 months ago

Physical access is root access, always has been

[-] umbrella@lemmy.ml 51 points 4 months ago

Despite being potentially catastrophic, this issue is unlikely to impact regular people. That’s because in order to make full use of the flaw, hackers would already need deep access to an AMD-based PC or server.

[-] PoopMonster@lemmy.world 22 points 4 months ago

"FUCK!" - Intel execs

[-] tal@lemmy.today 42 points 4 months ago* (last edited 4 months ago)

Now onto some better news. Despite being potentially catastrophic, this issue is unlikely to impact regular people. That’s because in order to make full use of the flaw, hackers would already need deep access to an AMD-based PC or server. That’s a lot of work for a random home PC, phew, but could spell trouble for corporations or other large entities.

Hmm.

It does mean that any secondhand computer or CPU (or even CPU from a sketchy source) could be compromised prior to being physically sold.

I have worried a bit before about the physical supply chain. Consider this case, earlier in the year, about someone selling counterfeit Cisco hardware (not intending to compromise computers, just make a buck):

https://www.justice.gov/opa/pr/leader-massive-scheme-traffic-fraudulent-and-counterfeit-cisco-networking-equipment

“Aksoy sold hundreds of millions of dollars’ worth of counterfeit computer networking equipment that ended up in U.S. hospitals, schools, and highly sensitive military and other governmental systems, including platforms supporting sophisticated U.S. fighter jets and military aircraft,” said Principal Deputy Assistant Attorney General Nicole M. Argentieri, head of the Justice Department’s Criminal Division. “Criminals who flood the supply chain with low-quality networking equipment from China and Hong Kong harm U.S. businesses, pose serious health and safety risks, and compromise national security. This case—one of the largest counterfeit trademark cases ever prosecuted in the United States—demonstrates the Criminal Division’s commitment and capacity to prosecute the most complex counterfeiting schemes and bring the perpetrators to justice.”

“Through an elaborate, years-long scheme, Aksoy created and ran one of the largest counterfeit-trafficking operations ever,” said Attorney for the United States Vikas Khanna for the District of New Jersey. “His operation introduced tens of thousands of counterfeit and low-quality devices trafficked from China into the U.S. supply chain, jeopardizing both private-sector and public-sector users, including highly sensitive U.S. military applications like the support platforms of U.S. fighter jets and other military aircraft. Yesterday’s sentence, made possible by the investigation and prosecution of this office and our department and agency partners, now brings Aksoy to justice and holds him accountable for the breathtaking scale of his operation.” 

According to court documents and statements made in court, Aksoy ran at least 19 companies formed in New Jersey and Florida, as well as approximately 15 Amazon storefronts and at least 10 eBay storefronts (collectively, the Pro Network Entities). The Pro Network Entities imported from suppliers in China and Hong Kong tens of thousands of low-quality, modified computer networking devices with counterfeit Cisco labels, stickers, boxes, documentation, and packaging, all bearing counterfeit trademarks registered and owned by Cisco that made the goods falsely appear to be new, genuine, and high-quality devices manufactured and authorized by Cisco. The devices had an estimated total retail value of hundreds of millions of dollars. The Pro Network Entities generated over $100 million in revenue from the scheme, and Aksoy personally received millions of dollars.

I remember that that hardware made it into even Cisco's own authorized partners' inventory.

And that's not something that's gonna be far up in the supply chain. People don't build Cisco hardware into a lot of other products.

So you gotta wonder what can happen if someone has a good way to undetectably compromise CPUs and insert them into the supply chain.

[-] DrDominate@lemmy.world 18 points 4 months ago

Unless I'm mistaken, the malware isn't on the CPU. The exploit is CPU, but the firmware is stored on the bios chip. Used motherboards are a potential for having malware on them, but then again they always have been a risk

[-] db2@lemmy.world 6 points 4 months ago

It does mean that any secondhand computer or CPU (or even CPU from a sketchy source) could be compromised prior to being physically sold.

It's worse than that, any AMD chip from any source except maybe AMD directly is suspect. Mine is a few years old from Amazon supposedly new, for all I know it came compromised and is sitting there doing what I tell it to until it triggers and I won't even know when or if it happens.

[-] SupraMario@lemmy.world 2 points 4 months ago

That's not how this exploit works at all...you have to have physical access to the machine basically. This is a nothing burger.

[-] db2@lemmy.world 4 points 4 months ago

That's to get it installed, not if it's already there.

load more comments (5 replies)
load more comments (5 replies)
[-] rc__buggy@sh.itjust.works 4 points 4 months ago

Oh man, the Pro Networking scandal is so funny to me. I wonder how many of those machines are out there running IOS right now and no one is the wiser. AFAIK there aren't allegations of backdoors or anything, just fake Cisco gear.

[-] some_guy@lemmy.sdf.org 2 points 4 months ago

This is an attack vector that hadn't occurred to me and I find it disturbing. Wow.

[-] Cocodapuf@lemmy.world 2 points 4 months ago

It does mean that any secondhand computer or CPU (or even CPU from a sketchy source) could be compromised prior to being physically sold.

Does it mean that? I mean a computer bought from a sketchy source, sure. But just a cpu alone? Do these raptor lake cpus have any non volatile memory? Because if not, then a second hand cpu is totally safe.

[-] AnUnusualRelic@lemmy.world 36 points 4 months ago

It was really just a matter of time before someone figured a way to exploit those stupid deep management engines. It was so predictable.

And each intel chip runs a minix system behind the scenes that I'm sure someone will soon find a way to play with if it's not already compromised.

[-] Kazumara@discuss.tchncs.de 11 points 4 months ago* (last edited 4 months ago)

And each intel chip runs a minix system behind the scenes that I’m sure someone will soon find a way to play with if it’s not already compromised.

There was a big story of an expoit of the Intel ME already. I think it was this: https://www.intel.com/content/www/us/en/support/articles/000025619/software.html from Positive Technologies at BlackHat 2017

[-] jet@hackertalks.com 33 points 4 months ago* (last edited 4 months ago)

Sinkclose

Impacted systems: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html

Original presentation details. https://ioactive.com/event/def-con-talk-amd-sinkclose-universal-ring-2-privilege-escalation/

This is a big f****** deal. If you get kernel access to a system, which is not uncommon, you can install a persistent back door that subverts the rest of the system forever. That's huge. It does not require physical access, requires kernel access.. different things

Steam games that ask for admin privileges, a USB stick that boots, normal virus infection that can never be uninstalled,. persistent RAT....

[-] flying_sheep@lemmy.ml 17 points 4 months ago

Negative rings are a horrible proprietary liability.

That's been clear from their inception, and this changes nothing.

[-] Kazumara@discuss.tchncs.de 24 points 4 months ago* (last edited 4 months ago)

What the heck? Then get to planning you dicks?

[-] curiousaur@reddthat.com 11 points 4 months ago
[-] Kazumara@discuss.tchncs.de 4 points 4 months ago* (last edited 4 months ago)

For all the others on the page they are planning fixes, only Mattisse has this. Is there something special about Matisse compared to the others?

load more comments (1 replies)
[-] cpw@lemmy.ca 10 points 4 months ago

I'll bet the Intel management engine is just as "vulnerable". The only context this is likely a concern is large scale corpo deployments, without verified supply chains to the source. Love how the security researcher handwaves that there's "plenty of existing exploits" that can be used to install the exploit into the SMM, without giving any suggestions of how.

[-] aaaaace@lemmy.blahaj.zone 5 points 4 months ago

No way that Intel sat on this for years until they needed it for PR.

[-] Imgonnatrythis@sh.itjust.works 4 points 4 months ago

I was troubled by how many times this article used the word "deep". Also, what was the bit about the hack likely surviving a reinstall of the OS? Why in the world wouldn't it if it's a cpu bios firmware hack?

[-] bruhduh@lemmy.world 3 points 4 months ago

Deep thoughts with deep

load more comments
view more: next ›
this post was submitted on 10 Aug 2024
210 points (83.0% liked)

Technology

60082 readers
3220 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS