PCgamer324

true, but if my sources are correct we could see a physical attack vector as well, such as a malicious USB drive gaining access to the UEFI RX bus. I am not particularly familiar with the intricacies of BIOS connectivity and operation; any further details you could share on the subject would certainly contribute to the topic at hand, particularly on how and when devices can write to such chips

I'm not even sure which are relevant and the entire topic makes 0 sense

no its not possible; I can already think of 20+ legal and technical problems you'd have with building this; outside of the premise making no sense and costing multiple hundreds of thousands of dollars

Given that this affects Lenovo and HP units that use consumer-oriented chipsets, I don't think that non-Z boards are any different in that regard

(ignore comment; editor reposted the topic here when saving for some reason)

given ties to Intel Reference Code, I wouldn't say anyone using UEFI or particularly Gigabyte/Intel is out of the woods yet. It's relatively impossible for a security research to test all of a companies product line alone.

yeah no... just no

it's unclear at this time

I edited the post, but from what I'm seeing the exploit seems to be a derivative of Intel Reference Code. This could insinuate that AMD is not affected, but we do not know at this time

Source 1: http://www.theregister.co.uk/2016/07/06/nasty_bios_bug_slugs_gigabyte_hackers_say/ Source 2: http://www.theregister.co.uk/2016/07/04/lenovo_scrambling_to_get_a_fix_for_bios_vuln/ Inherent vulnerabilities in UEFI are finally catching up with consumer motherboard manufactures; notably Lenovo, HP and even Gigabyte... Affected units have expanded to "enthusiast-grade" motherboards such as members of the "Ultra Durable" series It is suggested that if you use a Lenovo or HP system or one of the affected Gigabyte motherboards that you follow this story closely and patch as soon as a fix is made available. Such low-level level exploits could damage components, create hardware-level backdoors and even spread to USB and PCIe devices. given ties to Intel Reference Code, I wouldn't say anyone using UEFI or particularly Gigabyte/Intel is out of the woods yet. It's relatively impossible for a security research to test all of a companies product line alone. We'll have to wait for this to pan out... [UPDATE] Further tweets from the researchers behind this exploit suggest all SandyBridge - Broadwell systems are affected: Dell and Fujitsu also effected:

3.0ghz x 2 cores (lower than maximum multiplier for power savings) Apple used to do this too with Xserve:

"give a man a zero-day and he'll have access for a day; teach a man to phish and he'll have access for life..."

Um... this won't even work lmao... X48 and X38 do not support 5-series 771 xeons, only P-series chipsets

OSX PowerUsers rejoice! Finally a better filesystem I might actually upgrade from mavericks to Sierra

"Military's Telnet service..." "...enhancing its security" >telnet >security

why the fuck would you want to move to pollution and radiation island and furthermore why would you want to become a self-proclaimed Weeaboo... you need to rethink life sir

stop trying to be edgy

wow another human among billions completes 12 years of textbooks and has the option of continuing on to complete more textbooks in exchange for money guess what no one cares

ah okay thanks for the info

I don't know the full story, but I thought Pascal had an on-chip Vin watchdog...

2.8ghz at 1.06v; that seems a bit odd... Is there a chance Kingpin confusing the chip as to what to Vin was with some software tricks to bypass 1.25v voltage cap?

@Lays any idea what's up with the GPU voltage here?

@thekeemo I thought you were ex-muslim anyway...