home.social

#sinkclose — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sinkclose, aggregated by home.social.

  1. Security Alert: AMD Sicherheitslücke Sinkclose

    Es wurde eine sehr schwerwiegende, wenn auch nur schwierig auszunutzende Sicherheitslücke (setzt Kernel-Zugriff voraus) in AMD-CPUs gefunden. Die Lücke betrifft praktisch alle CPUs der letzten 18 Jahre. kantel.github.io/posts/2024082 #Update #Security #AMD #Sinkclose #Linux

  2. Cette faille #sinkclose semble être traitée avec beaucoup de légèreté par #AMD. Ils proposent des solutions... mais pas pour les ryzen 3000 ?? C'est du foutage de gueule, ou il me manque du contexte ?

    Via @nextinpact next.ink/146424/sinkclose-tous

  3. #AMD Issues Updates for Silicon-Level 'SinkClose' Processor Flaw

    SinkClose flaw in SMM on AMD EPYC (data center chips) and various Ryzen models can allow threat actor to drop #malware deep enough in a system that the operating system or the hyper visor wouldn’t be able to detect it.

    Attackers require kernel-level access to exploit this; but put into context, kernel-level access is a substantial pwn in itself. Chances are even before an attacker could obtain kernel-level access, you’d already have major problems.

    AMD has issued #firmware updates and mitigations for various models.

    #cybersecurity #infosec #sinkclose

    darkreading.com/remote-workfor

  4. Patched my desktop PC for the Sinkclose (CVE-2023-31315) AMD cpu hardware vulnerability.

    Of course, as always, the MSI firmware upgrade, nuked my Linux boot loader out of the EFI and I had to use a USB live-media to manually fix that using a grub-install ...

    #linux #msi #bios #update #security #cve_2023_31315 #sinkclose

  5. Anyone got any more detail of the #amd #sinkclose bug?
    I found a 'redacted' version of the Defcon PDF; it seems to be suggesitng poking the 'top of memory' msr and then getting the hardware confused between PCI/RAM/etc - but most of the slides are missing:

    media.defcon.org/DEF%20CON%203

  6. #CyberSecurity #AMD #Sinkclose #ComputerBugs #Vulnerability: "Now security researchers have found one such flaw that has persisted in AMD processors for decades, and that would allow malware to burrow deep enough into a computer's memory that, in many cases, it may be easier to discard a machine than to disinfect it.

    At the Defcon hacker conference, Enrique Nissim and Krzysztof Okupski, researchers from the security firm IOActive, plan to present a vulnerability in AMD chips they're calling Sinkclose. The flaw would allow hackers to run their own code in one of the most privileged modes of an AMD processor, known as System Management Mode, designed to be reserved only for a specific, protected portion of its firmware. IOActive's researchers warn that it affects virtually all AMD chips dating back to 2006, or possibly even earlier."

    arstechnica.com/security/2024/

  7. Wie schwerwiegend #sinkclose ist, ordnet @heiseonline aber richtig ein:

    »Ein vergleichbarer Fehler führte im Mai 2015 zum kompletten Austausch der Hardware des Bundestages, wie heise online berichtete. Angreifer hatten damals Computer in zahlreichen Abgeordnetenbüros mit Spionagesoftware infiziert, darunter auch Rechner im Bundestagsbüro von Kanzlerin Angela Merkel (CDU).«

    Das wäre auch diesmal u.U. angebracht, denn Wire zitiert die Entdecker der Sicherheitslücke folgendermaßen:

    “Imagine nation-state hackers or whoever wants to persist on your system. Even if you wipe your drive clean, it's still going to be there,” says Okupski. “It's going to be nearly undetectable and nearly unpatchable.” Only opening a computer's case, physically connecting directly to a certain portion of its memory chips with a hardware-based programming tool known as SPI Flash programmer and meticulously scouring the memory would allow the malware to be removed, Okupski says.

    Nissim sums up that worst-case scenario in more practical terms: “You basically have to throw your computer away.”

  8. Flaw in Hundreds of Millions of Chips Allows Deep, Virtually Unfixable Infections

    wired.com/story/amd-chip-sinkc

  9. #Sinkclose’ Flaw in Hundreds of Millions of #AMD Chips Allows Deep, Virtually Unfixable Infections

    Researchers warn that a bug in AMD’s chips would allow attackers to root into some of the most privileged portions of a computer
    —and that it has persisted in the company’s processors for decades.

    The flaw would allow hackers to run their own code in one of the most privileged modes of an AMD processor,
    known as System Management Mode, designed to be reserved only for a specific, protected portion of its firmware.

    IOActive's researchers warn that it affects virtually all AMD chips dating back to 2006, or possibly even earlier.

    wired.com/story/amd-chip-sinkc

  10. what is happening with all the processors? why is there every month a new devastating vulnerability?
    #intel #amd #sinkclose

  11. Es gibt eine Lücke in Prozessoren, die Angreifer*innen, die bereits Kernelrechte erreicht haben, ein permanentes Einnisten im System ermöglicht. Dabei agieren sie auf einer Ebene unter Hypervisor oder Kernel und bleiben so vor Betriebssystem und Malwarescannern versteckt. Um Code zu entfernen reicht eine Neuinstallation des Betriebssystems nicht aus, da sich so persistierter Schadcode in den Ebenen darunter befindet.

    Angreifer*innen benötigen vorher bereits eine Lücke, die Ausführen von Code mit Kernelrechten im Prozessor erlaubt. Erst dann können sie die neue Lücke nutzen, um Code noch tiefer im System zu verankern.

    golem.de/news/sinkclose-trifft

    #itsicherheit #itsecurity #infosec #sinkclose #CVE-2023-31315

  12. Almost unfixable “Sinkclose” bug affects hundreds of millions of AMD chips - Security flaws in your computer's firmware, the deep-seated code that loads first ... - arstechnica.com/?p=2042298 #syndication #sinkclose #security #amd #cpu

  13. La placa base tiene un reprogramador por hardware así que la actualizaré de esa manera después de estar disponible la corrección de #sinkclose.

  14. #sinkclose, una vulnerabilidad que ha cumplido la mayoría de edad sin que nadie lo supiera.

    tomshardware.com/pc-components

    Los procesadores viejos no recibirán parche en UEFI o BIOS (amd.com/en/resources/product-s).

    El caso es que voy a comprobar las actualizaciones de UEFI de la placa base y veo que hay una nueva versión disponible pero no es por este fallo. Es por otro, CVE-2024-36877 (github.com/jjensn/CVE-2024-368) que también afecta al modo #SMM.

    Así que aún tiene que salir otra actualización que corrija sinkclose, CVE-2023-31315.

    Joer qué suerte.

    Estas vulnerabilidades requieren acceso total al sistema operativo, momento en el que el atacante puede hacer lo que le dé la gana como por ejemplo intentar entrar en areas protegidas por el hardware y ganar permanencia escribiendo en el firmware, que es lo que tratan estas dos vulnerabilidades.

  15. AMD Sinkclose: Universal Ring-2 Privilege Escalation

    When researching the AMD processor, our team noticed a flaw in one of the critical components required for securing SMM. This silicon-level issue appears to have remained undetected for nearly two decades.

    ioactive.com/event/def-con-tal

    amd.com/en/resources/product-s

    #AMD #SMM #Sinkclose