fubarx@lemmy.world to Technology@lemmy.worldEnglish · 7 days agoCode-execution flaw in UEFI firmware affects most servers on planet Eartharstechnica.comexternal-linkmessage-square99linkfedilinkarrow-up1454arrow-down19file-text
arrow-up1445arrow-down1external-linkCode-execution flaw in UEFI firmware affects most servers on planet Eartharstechnica.comfubarx@lemmy.world to Technology@lemmy.worldEnglish · 7 days agomessage-square99linkfedilinkfile-text
minus-squarenightwatch_admin@lemmy.worldlinkfedilinkEnglisharrow-up7·6 days agoYes, actual BIOSes have no network access. They had other issues though, like enough space to embed hidden persistent malware, writable from Windows.
minus-squareThe_Decryptor@aussie.zonelinkfedilinkEnglisharrow-up2·6 days agoNah, PXE predates UEFI by like 20 years, it’s been a pretty normal feature since the late 80s.
minus-squarenightwatch_admin@lemmy.worldlinkfedilinkEnglisharrow-up1·2 days agoiirc you cannot modify a bios in a pxe context, but I might be mistaken.
minus-squareThe_Decryptor@aussie.zonelinkfedilinkEnglisharrow-up1·8 hours agoThere’s probably flaws that would allow executing attacker supplied code, but it’s not like BIOSs had any notion of security (i.e. secure boot) to begin with, so you could just straight up have the system boot into your own image anyway.
Yes, actual BIOSes have no network access. They had other issues though, like enough space to embed hidden persistent malware, writable from Windows.
Nah, PXE predates UEFI by like 20 years, it’s been a pretty normal feature since the late 80s.
iirc you cannot modify a bios in a pxe context, but I might be mistaken.
There’s probably flaws that would allow executing attacker supplied code, but it’s not like BIOSs had any notion of security (i.e. secure boot) to begin with, so you could just straight up have the system boot into your own image anyway.