Wednesday, March 14th 2018
CTS Labs Sent AMD and Other Companies a Research Package with Proof-of-Concept Code
CTS Labs, the Israel-based IT security research company behind Tuesday's explosive AMD Ryzen security vulnerabilities report, responded to questions posed by TechPowerUp. One of the biggest of these, which is also on the minds of skeptics, is the ominous lack of proof-of-concept code or binaries being part of their initial public report (in contrast to the Meltdown/Spectre reports that went into technical details about the exploit). CTS Labs stated to TechPowerUp that it has sent AMD, along with other big tech companies a "complete research package," which includes "full technical write-ups about the vulnerabilities," "functional proof-of-concept exploit code," and "instructions on how to reproduce each vulnerability." It stated that besides AMD, the research package was sent to Microsoft, HP, Dell, Symantec, FireEye, and Cisco Systems, to help them develop patches and mitigation.
An unwritten yet generally accepted practice in the IT security industry upon discovery of such vulnerabilities, is for researchers to give companies in question at least 90 days to design a software patch, harden infrastructure, or implement other mitigation. 90 days is in stark contrast to the 24 hours AMD got from CTS Labs. CTS Labs confirmed to TechPowerUp that it indeed shared its research package with AMD (and the other companies) just 24 hours prior to making its report public, but urged those disgruntled with this decision to look at the situation objectively. "If you look at the situation in the following way: right now the public knows about the vulnerabilities and their implications, AMD is fully informed and developing patches, and major security companies are also informed and working on mitigation."This is in contrast to the unintentional consequence of keeping Meltdown/Spectre away from the public domain for over half a year, allowing Intel's senior executives to dump company stock, and for big cloud computing providers to harden their infrastructure, giving themselves a competitive advantage over smaller providers. But unlike with Meltdown/Spectre, these vulnerabilities aren't industry-wide (i.e. they don't affect Intel), placing AMD at a disadvantage in both the stock markets, and in the retail markets.
CTS Labs, through the sequence of its actions, has attempted to shift the burden of proof from itself to AMD, which is extremely uncommon in the IT security industry. With the lack of proof-of-concept of these vulnerabilities in the public domain, an environment of fear, uncertainty, and doubt (FUD) is being developed, with AMD being occupied with testing its chips for these vulnerabilities, and still far away from releasing patches, if the vulnerabilities are real. This places anyone with a shorting position against AMD stock at a distinct advantage. The strategy of AMD investor relations and corporate communications should now be to allay many of those fears among people without access to the proof-of-concept, and to ask investors to refrain from giving in to FUD.
An unwritten yet generally accepted practice in the IT security industry upon discovery of such vulnerabilities, is for researchers to give companies in question at least 90 days to design a software patch, harden infrastructure, or implement other mitigation. 90 days is in stark contrast to the 24 hours AMD got from CTS Labs. CTS Labs confirmed to TechPowerUp that it indeed shared its research package with AMD (and the other companies) just 24 hours prior to making its report public, but urged those disgruntled with this decision to look at the situation objectively. "If you look at the situation in the following way: right now the public knows about the vulnerabilities and their implications, AMD is fully informed and developing patches, and major security companies are also informed and working on mitigation."This is in contrast to the unintentional consequence of keeping Meltdown/Spectre away from the public domain for over half a year, allowing Intel's senior executives to dump company stock, and for big cloud computing providers to harden their infrastructure, giving themselves a competitive advantage over smaller providers. But unlike with Meltdown/Spectre, these vulnerabilities aren't industry-wide (i.e. they don't affect Intel), placing AMD at a disadvantage in both the stock markets, and in the retail markets.
CTS Labs, through the sequence of its actions, has attempted to shift the burden of proof from itself to AMD, which is extremely uncommon in the IT security industry. With the lack of proof-of-concept of these vulnerabilities in the public domain, an environment of fear, uncertainty, and doubt (FUD) is being developed, with AMD being occupied with testing its chips for these vulnerabilities, and still far away from releasing patches, if the vulnerabilities are real. This places anyone with a shorting position against AMD stock at a distinct advantage. The strategy of AMD investor relations and corporate communications should now be to allay many of those fears among people without access to the proof-of-concept, and to ask investors to refrain from giving in to FUD.

93 Comments on CTS Labs Sent AMD and Other Companies a Research Package with Proof-of-Concept Code
I should warn you though, get ready to be sorely disappointed, as the news on these flaws have been reported on almost every single reputable tech site, and even on non tech related news websites, so you'll have to deal with the fact that this is a newsworthy development, I would suggest avoiding reading about it if it rubs you in such a wrong way.
As far as W1zzard's credentials, he's been developing hardware level hacking tools since the days when Ati was still around, I remember using his OCing tools back when I had a Radeon 8500 in the early 2000s, so give the man some credibility, that gives him a fair advantage when formulating a well educated guess on the veracity of these alleged flaws.
Either way, this is a tech site, and TPU has every right to report on these very relevant news, they can't just turn a blind eye, or bury their heads in the sand while everyone else is reporting on it.
Idk why people are rushing to conclusions without even hearing from AMD, obviously this has caught the tech world by surprise, I strongly advise to wait for an official acknowledgement by AMD before formulating theories about the origins of the vulnerabilities, and the extent of damage we can expect from them if they're in fact real.
Anyway, it may be a couple of days before we hear anything from AMD. As I understand things, third party validation took 4-5 days.
That said, I just noticed an update in the AT from this morning that may clarify one thing or another... or not.
[INDENT][/INDENT]
"Breaking an Entering" vs "Trespassing" your still not authorized to be there. Heck you can Trespass through a open door.
Well if i put a uniform and disguise myself as a cop (signed credentials) its okay right? What ever I do there after is there for a vulnerability.Going to put a lot of strippers out of work
How is Ryzen more adversely impacted than a Core i7 once root access is gained? In either case, I'd argue you already lost the war. Why do these 13 vulnerabilities matter at all? It's like comparing the aftermath of an ant invasion versus a earwig invasion. Full damage control mode response is more or less the same, no?
Yes.That's been false since "hardware security" became a thing.
Or, it was supposed to be.Because linux doesn't run on the PSP?
But yeah 24 hours is too short time to respond and makes all this very suspicious. Makes it feels like a stock manipulation scam disguised with real but not so severe vulnerabilities.
Well, now we know that AMD has a similar extra CPU core that does management on their processors. However, they use an ARM Cortex based core. And it seems their checks to making sure the management engine isn't replaced with malicious content are not as hard to crack as Intel's. Allowing malicious code to much more easily be injected into the management engine. And once the malicious code is in the management engine, it is going to be extremely difficult to get out. These are low level functions of the CPU that normally have no real exposure to the OS, or even the BIOS.
That's all assuming that we believe CTS. Which I'm still hesitant to do. I believe they are doing this just to make a name for themselves.
otherwise just make your own driver driver that does pci config space accesses through cf8, to find out mmio ranges and then write to these or map into user-space
the claim by cts is that the firmware hash checks on bootup can be bypassed
developer.amd.com/amd-secure-memory-encryption-sme-amd-secure-encrypted-virtualization-sev/
Of course we don't know what kind of operating system it is running. The vulnerabilities in Intel ME were exposed when it was discovered it was a branch of Linux.
Edit: Looks like Secure Processor might be open sourced. Maybe not all of it but:
github.com/AMDESE/AMDSEV
Edit: So yeah, AMD needs to push an update out for the Secure Processor to shut down the holes that were discovered. That sounds important, yeah, and another strike against the secure processor inside of the processor but it definitely doesn't warrant all the fanfare that was generated.