Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.
*Cries in 5 2600 and 1070*
you and me both my friend, you and me both… except for the fact that im still vibing with them. EVGA 1070, i don’t want to give it up F
My EVGA GTX 1070 SC Gaming ACX 3.0 Black Edition is also holding up strong, especially with AMD FSR or good games (like Metro), but 4k is really bad for the poor little guy :c
But even with my new PC, he will continue to live in my server :3
yeah, i’m gaming on 1080 and mostly playing minecraft and factorio though, so im not exactly gunning for FPS there. I will keep this card until it dies dead properly, and then it will become wall art.
How severe is this vulnerability?
You need to be a root to exploit it, but if it get exploited any way to get rid of it is to throw MB to trash.
Patch/reflash with a new bios?
How do you trust that the flash was done properly if you did it from the compromised system? This would only work if you flashed it externally somehow without the system running.
¯\_(ツ)_/¯
Exactly. That’s why it’s a trash motherboard as soon as root access is gained. It can never again be trusted.
A flash programmer
deleted by creator
The good news is that in order to exploit the new vulnerability, the attacker first has to obtain kernel level access to the system somehow - by exploiting some other vulnerabilities perhaps.
The bad news is once Sinkclose attack is performed, it can be hard to detect and mitigate: it can even survive an OS reinstall.
The other bad news: there are so many vulnerabilities on all systems which can be used to gain root-level access, it’s just a matter of time. Also, even future vulnerabilities will be an issue, as the underlying Sinkclose attacks will still work.
Honestly not on a hardened setup
Sure, if you’d rather like to believe that.
If it was that easy to get root then we would be in serious trouble. The best way I can think of is social engineering.
So basically what you are saying is we just need one pvp game with kernel level anti cheat to fuck up somewhere… yeah I’m sure that’s not going to happen.
Probably only on a targeted attack. I don’t see it being a mass target attack like a worm could be.
And in the realm of businesses, how many programs are running in kernel level besides the antivirus/ED(P)R solution?And with crowd strike we have seen how reliable Antivirus is.
I don’t see it being a mass target attack like a worm could be.
Why not? Malware that survives a full new install is extremely valuable, and there are loads of games adding vulnerabilities with required kernel level rootkits. It’s only a matter of time until one of these vendors is exploited, and why wouldn’t you permanently own the significant chunk of the market with unpatched serious vulnerabilities while you’re at it?
Again: Mass spread vs target attack.
Remember WannaCry? Yeah, I don’t see that happen.
But (industrial) e-spionage on the other hand? Yup. Will happen 100%For what reason?
Kernel level game anticheats are a great attack vector, and it’s one that inherently identifies and enables distribution to other vulnerable targets. It’s begging to self replicate.
Industrial espionage does not make sense, because most enterprises have, even if imperfect, restrictions on what can be installed on company computers that contain valuable information. You’re not going to get a game with kernel malware on a managed enterprise computer.
Are you ignoring what I wrote earlier in the same thread?
Probably only on a targeted attack. I don’t see it being a mass target attack like a worm could be. And in the realm of businesses, how many programs are running in kernel level besides the antivirus/ED(P)R solution?
Anyway. Counter question: Why do you think gamers appear as a more valuable target with the anti cheat as a possible attack vector vs a business running literally the same CPU line-up but with fewer kernel level programs?
My personal opinion: You can’t extract as much money from private folks vs a business through blackmail and other solutions. Not in a wide casted attack.
Targeted individuals can be assumed to be at a higher risk (e.g. hacking their private devices like the gaming pc and then doing home office work in the same network, or misusing trust in the home network between pc and phone and then installing malware like pegasus).
But again: Not in a wide casted net. And you are probably better of using the good exploits for higher value targets.
The USB and network stack
we just need one pvp game with kernel level anti cheat
Leaving aside that security patches should be done, if you install that kind of game on a system where you have any data worth protecting, you’re a dumb ass mtherfcker. Sorry, but seriously, that’s just how it is.
Ignorance is not stupidity.
Despite this being reported on tech news, most people won’t even be aware that it’s a thing because most people won’t actually read about it. And the majority of gamers probably don’t even know what a kernel is or why an anti-cheat with elevated privileges would be a bad thing.
Most people buy their computers with Windows preinstalled and probably couldn’t tell you if the CPU is Intel or AMD.
Okay, fair point, let me rephrase: if someone knows what kernel (admin) level execution means, and installs a game that requires this on a computer where they keep important data, they are a dumbass mtherfcker :) Generally speaking though: most people shouldn’t be allowed to use technology - humans are unbelievably stupid for the most part.
Kernel level and admin level is not the same thing. For example on windows, you can’t really write your own kernel driver, and on Linux even root can’t do everything if capabilities have been revoked.
For the purpose of protecting important data, the distinction really doesn’t matter. And the good old xkcd comic has a point - for many people, all relevant data is in the user’s accessible storage area anyways. Hence me running almost all internet applications and steam in a jail.
custom firmware!
Does not exist for Ryzen because of AGESA licensingnq
Arrrr?
The fuck are you trying to say? Speak English. Also no one at coreboot has publicly released (or developed?) anything for AM4 and you can’t access AGESA code to patch it yourself.
removed by mod
I don’t think they’re suggesting taking it away from the rightful owner.
removed by mod
deleted by creator
welp, time to go buy intel… wait.
You laugh, but if you’re buying used, this 100% makes Intel the way to go over a Ryzen 1000/2000/3000 CPU.
as long as we’re buying 12th gen, we’re ok.
I dont know.
If I had my choice between a CPU that has a vulnerability that can only be exploited if the system is already compromised
or a CPU that are full of oxidation cancer, or frying themselves and doing irreparable damage… Which the company is being excessively shady about concretely admitting to any RMA promises and wwill all eventually die in short order…
I think I’m gonna go with the Ryzen and not leave leave my computer outside at defcon.
Sure but we’re talking about several generation old CPUs: nothing’s wrong with Intel’s 10/9/8th gen CPUs, which would be the contemporary ones to the Ryzen chips in question.
Risc-V is the real response to this problem
How is that? Does risc-v have magical properties that make its designers infallible, or somehow make it possible to fix flaws in the physical design after the CPU has already been fabbed and sold?
Because it does not set in stone that there can be only 2 companies producing compatible chips, which can be however bad until both of them does the same shit practices.
So the short answer is by not stifling competition.
So what you are saying is, it’s just as Risc-E
As much as I like RISC-V, it is kind of ironic to suggest RISC-V ist the solution to this. At least as it stands, because of RISC-V’s simplicity, most if not all current RISC-V CPUs don’t even run microcode, so there is nothing to update/fix in case of a CPU bug. There’s even a very current example of this problem with that chinese RISC-V cpu that has this “GhostWrite” bug that allows every unpriviliged process to gain root access.
As I said in an other reply, RISC-V is not the solution for the reason that they are perfect today. It is because it is not limited to being used by a few megacorporations that do whatever they want, but it allows competition where companies do what they need to become and remain a good choice.
Now we just need a friendly neighbourhood nanoscale fab.
I understood that. My point was rather that in this particular case (a CPU bug that could be fixed via microcode, but AMD chose not to do so for certain CPUs), RISC-V wouldn’t have been of any advantage, because there would be nothing to fix in the first place. Sure, one could introduce microcode for RISC-V and people have argued in favor of doing so for this exact reason, but the architecture was intentionally designed to not require microcode.
removed by mod
removed by mod
wake up samurairemoved by mod
you need a mental evaluation
removed by mod
please seek help
removed by mod
Can you rub those 2 braincells together any faster might help some not enough probably
so that means you can internally flash the bios chip from the os?
would be cool if there were coreboot builds for these platforms, this exploit seems pretty useful
Wait yeah can someone explain why this exploit couldn’t be used to say rewrite it to support coreboot and turn this into a good thing?
because you need the coreboot people to write firmware that can initialise the system, and that probably takes a lot of reverse engineering
I don’t know much about this, but I assume there’s little to no effort for corebooting on the amd side, I’ve only seen intel platforms with coreboot
There are coreboot AMD projects for the framework laptop
Basically, reflash spi chips and it’ll be gone, and to be infected by that, person gotta have physical access to hardware he hacks, and physical access is root access as always has been
Nope. You do not need physical access for it, just root access. and you HW is compromised with only means to recover it is SPI flashing of CPU.
Shit, I have desktops running with 2200G and 2400G.
lol for the past 15 years I have “rebuilt” my desktop every 5 years but I didn’t expect the would try to force me out of my 7 3700x right on the date
Which is a shame because our 3700X is still pretty potent for the average user or gamer.
Yeah, I have been eyeing upgrades to get avx512 anyway because lately I have been doing very heave very low preset av1 encodes but when they are a dick about it I just feel like postponing it.
At launch, I’ve upgraded my system to a 3900x, and even today, it fulfills my cpu needs. This thing is incredible
Yea i got the 3900xt when i built my pc during covid. Love it but i had to disable a bunch of shit to prevent bluescreens from hypervisor shit
Welp, glad I avoided that
Yay, another BIOS update!
I am getting so sick of all these BIOS updates because of all these security vulnerabilities all the time. It is so tiring having to set up my settings all over again all of the time. Earlier this year, or maybe it was last year, it felt like every month or two there was a new BIOS update for a new security vulnerability.
Back your settings up and restore them then.
Depending on your BIOS and/or motherboard, you can’t restore them between versions. The point of clearing the BIOS settings after flashing a new version is to ensure that you only have values that are expected, which is why restoring backups can often be blocked between versions.
I learned this the hard way when I lost all my fan profiles
Thankfully that’s one thing that can be restored between BIOS versions for my motherboard lol
Not on mine :(
Really not good enough from AMD. I wonder if Intel wasn’t a complete dumpster fire right now if they would still cut off the fix at Zen 3 (I doubt it). There’s really no reason not to issue a fix for these other than they don’t want to pay the engineers for the time to do it, and they think it won’t cost them any reputational damage.
I hate that every product and company sucks so hard these days.
deleted by creator
They did issue a fix: “Buy a new CPU please!”
That’s why they don’t mind the reputation hit. If 1 person swears allegiance to Intel as a result but 2 people buy new AMD chips, they’re still ahead. And people will forget eventually. But AMD won’t forget the Q3 2024 sales figures.
Well, guess who’s not buying next gen Ryzen?
They are doing similar stuff with deliberately delaying Linux driver capabilities for Radeon 7xxx series, to make more GPUs die out faster, by overheating (zero RPM fan until 60°+).
AMD has unfortunately a long history of abandoning products before its reasonable on its graphics division. Its not really acceptable, up until earlier this year my NAS/server was running a 3600 and its only for power saving purposes I changed that as its still a very workable CPU in that role.
Er I’m still running a FX-8350 as a gaming machine (not AAA games obviously). I had another one as a host for a few VMs and it was more than enough till the motherboard went. One day I’ll upgrade I guess.
I moved from an FX8350 to a R5 5600G a few years ago, having run it for about 9 years. Initially I didn’t think I’d notice much difference, but frankly it’s an entirely different ballgame.
Oh yeah I plan to update. But only when I really get annoyed.
Single core performance is niiice
Attackers need to access the system kernel to exploit the Sinkclose vulnerability, so the system would have to already be compromised. The hack itself is a sophisticated vector that is usually only used by state-sponsored hackers, so most casual users should take that into account.
So it’s a vulnerability that requires you to.already have been compromised. Hardly seems like news.
I can understand AMD only patching server chips that by definition will be under greater threat. On the other hand it’s probably not worth the bad publicity not to fix more.
I personally agree. I think it’s being somewhat overhyped. If step one is physical access to get things rolling… like for sure some machines are in more public areas than others. But for me, someone would have to break into my house first, then access my machine, just to run exploits later. The exploit is pretty massive, but I think needs to be tempered with “first they need physical access”. Because physically controlling machines has always been number 1 for security.
The reason that this is news is because it allows malware to embed itself into the processor microcode once kernel is breached. IE: If it is exploited for compromise, you either have to have the knowledge and hardware to reset the processor microcode manually (Requires an SPI flash tool) or you toss the hardware entirely. There’s no just ‘blow the drive away and reinstall the OS’ solution available.
And that introduces a specific type of supply chain threat: someone who possesses a computer can infect their own computer, sell it or transfer it to the target, and then use the embedded microcode against the target, even if the target completely reformats and reinstalls a new OS from scratch.
That’s not going to affect most people, but for certain types of high value targets they now need to make sure that the hardware they buy hasn’t already been infected in the supply chain.
This sounds weird. I was in the impression that operating systems load updated cpu microcode at every boot, because it does not survive a power cycle, and because the one embedded in the BIOS/UEFI firmware is very often outdated. But then how exactly can a virus persist itself for practically forever?
The OS can’t get to the point of loading cpu microcode without that outdated, embedded microcode. The reason it can persist is because there aren’t a lot of good ways to see what that UEFI microcode actually is once it’s installed. Plus, only the UEFI tells you that it has successfully updated itself. There is no other more authoritative system to verify that against. So the virus could just lie and say it’s gone and you would never know. Hence needing to treat it as the worst case scenario, that it never leaves.
I don’t think it gets to the microcode but the UEFI.
It’s important because it allows them to directly modify the CPU’s microcode. Basically, the CPU has its own set of instructions, called microcode, which controls how the chip functions on a physical level. If they manage to change your microcode, even a full system reformat won’t kill the virus; You’ll need to either re-flash the CPU (which is not something the standard user or even power user will know how to do) or replace the entire CPU.
That being said it builds up vulnerabilities in anti-cheats to another beautiful crowstrike like domino cluster fuck
