News for hackers. Stuff that matters.
Re:Our Interesting Call with CTS-Labs by mizzao on Thursday March 15, 2018 @09:57PM (#16598025)
Can you please elaborate?
Re:Our Interesting Call with CTS-Labs by Arbalest on Thursday March 15, 2018 @09:59PM (#16598030)
Gamers Nexus did a good video. Long story short, looks like an investment propaganda attempt to try and get a profit out of shorting AMD stock. Whether this is a cover for anything else is getting deep into conspiracy.

Edit: Not truly fake news

Re:Our Interesting Call with CTS-Labs by tptacek on Thursday March 15, 2018 @10:02PM (#16598034)
Except that we know it isn't fake, as Trail of Bits validated the findings and confirmed serious vulnerabilities.
Re:Our Interesting Call with CTS-Labs by ComputerGuru on Thursday March 15, 2018 @10:11PM (#16598073)
I have no doubt that the findings are real, but they are more along the lines of bugs rather than “halt the press” gaping security holes.

We’ve all publicly disclosed and written patches for countless security vulnerabilities in open source code that’s widely distributed with zero fanfare - not even a cve - because we realize the difference between a security bug and a world-stopping, corporation-killing security bug. And the arrogance of saying something along the lines of “if I gave them a day or a million years it wouldn’t matter because this bug is too big to fix,” is beyond comment.

At no point did I give RedHat 24 hours to patch something before coming out with a well-orchestrated PR campaign with the hype engine on overdrive. Just submit a patch, make sure they admit they’re wrong and will take the appropriate measures, and move on.

Now if they found a remote exploit that could let me run arbitrary code on any AMD processor even in a sandboxes environment... we’d be having a different discussion altogether.

Re:Our Interesting Call with CTS-Labs by tptacek on Thursday March 15, 2018 @10:15PM (#16598086)
If you have admin access to these machines, you can persist into the secure coprocessor. In the presence of these vulnerabilities, it is actually worse to have a secure coprocessor than not to have one at all. They are serious vulnerabilities; about the worst you can have in an enclave scheme. If SGX had a comparable problem, it would be headline news.

Does that mean the stock should head to zero, like some crazy prop trading firm claimed they should? The fuck should I know? I am cynical about the impact vulnerabilities have on stock prices and don't think consumers generally care.

Re:Our Interesting Call with CTS-Labs by ComputerGuru on Thursday March 15, 2018 @10:20PM (#16598107)
I’m with you, but again, context. A compromised machine used to be a hosed machine until you reinitialized the drive and started clean. People are just starting to wake up to the fact that there’s another computer in your computer to which the same maxims apply.

Anyone that is serious about security hopefully knows this.

(I have no skin in the AMD/Intel CPU game. Too many machines running both to bother. I can’t believe I have to say this on HN, it’s what I’d expect of [H]ard in 2004.)

Re:Our Interesting Call with CTS-Labs by MertsA on Friday March 16, 2018 @08:14AM (#16600078)
The thing that gets me is that they are simultaneously making claims that some of those vulnerabilities can't just be fixed with a quick firmware update and that they would allow for a backdoor that could never be removed. If the flaw that allows the attacker to overwrite the firmware with their own version can't be fixed in software then how exactly is the malicious firmware supposed to prevent its own removal?

One of those claims has to be false. If an attacker can shut the door behind them so to speak then it has to be possible for AMD to do the same.

Re:Our Interesting Call with CTS-Labs by fencepost on Thursday March 15, 2018 @11:27PM (#16598366)
Persistence is a big deal, but I can't help but feel a certain level of "meh" because my gut feeling is that persistence is a lot more useful in espionage and state actors than in the kind of business environments I deal with.

Maybe this is going to be the next big thing thrown into Metasploit so it can be easily used to make persistent something that's effective on a variety of systems with a variety of environments and data while still being subtle enough to avoid having the infection vector code make it into every AV package out there, but I doubt it.

To me the use of this kind of exploit feels like a very fine needle. Very fine needles are very very useful in a lot of specific situations, but very fine needles scattered haphazardly around the environment are a very different thing.

Re:Our Interesting Call with CTS-Labs by xeeeeeeeeeeenu on Thursday March 15, 2018 @10:10PM (#16598064)
No, they didn't confirm serious vulnerabilities. Excerpt from their blog:

>There is no immediate risk of exploitation of these vulnerabilities for most users. Even if the full details were published today, attackers would need to invest significant development efforts to build attack tools that utilize these vulnerabilities. This level of effort is beyond the reach of most attackers

Re:Our Interesting Call with CTS-Labs by cthalupa on Friday March 16, 2018 @12:41AM (#16598679)
None of that discounts these from being serious vulnerabilities. If you are utilizing the secure coprocessor on a machine that is tasked with keeping secrets secure, and you are worried about sophisticated attackers, then this is incredibly serious.

Just because it doesn't impact you, or the majority of users, does not mean it is not a severe issue. The majority of users are quite likely to be of low interest to attackers wanting to exploit the secure coprocessor in the first place.

Re:Our Interesting Call with CTS-Labs by hoistbypetard on Friday March 16, 2018 @03:13AM (#16599120)
> If you are utilizing the secure coprocessor on a machine that is tasked with keeping secrets secure, and you are worried about sophisticated attackers, then this is incredibly serious.

If you are worried about sophisticated attackers, and you are trusting a "secure coprocessor" with such an unspecified and undocumented interface as this, I'd argue that you have no reason to think that the tool you have chosen to defend against the threat you're worried about is adequate. Contrast a coprocessor with no documented security boundary (if I'm missing something on that front, please post a link!) against a traditional HSM. Sure, the latter have had some flaws too, historically, but the well-defined boundary is key to even being able to assess suitability. I've not seen any documentation of this coprocessor's interface/boundaries at all. Let alone any that approaches the level of detail you'd get with an HSM.

Re:Our Interesting Call with CTS-Labs by cthalupa on Friday March 16, 2018 @10:16AM (#16600787)
I'd agree there - but that doesn't stop AMD from advertising this as a function these CPUs provide, so if you've taken them at their word, this is a big deal.
Re:Our Interesting Call with CTS-Labs by Level3Basic on Thursday March 15, 2018 @10:07PM (#16598051)
Exactly. CTS May be sloppy or naive, but if the people they claim to have shared the vulnerabilities with have been verified, then there's no reason to think there's a Big Conspiracy of Stock Shorters here.
Re:Our Interesting Call with CTS-Labs by Arbalest on Thursday March 15, 2018 @10:07PM (#16598052)
Not truly fake, then again, a lot of propaganda is also based on an element of truth. Is there any meaningful distinction between propaganda and fake news?
Re:Our Interesting Call with CTS-Labs by tptacek on Thursday March 15, 2018 @10:09PM (#16598061)
https://www.youtube.com/watch?v=Kh0Y2hVe_bw

I accept with basically no questions that the announcement was coordinated to enable a stock-shorting scheme. You might be interested to know: this isn't the first time that's happened. I don't care. I don't think these stock-shorting schemes work. I agree with Matt Levine: attempts to profit from stock declines are far from the worst things people can do with vulnerability research --- for instance, they could collude with vendors to withhold disclosure for months or years, which is something that happens.

Where I have problems:

* When AMD fanatics try to spin the confusion about the story into a claim that CTS-Labs didn't find anything, which we know now to be false.

* When anybody reacts to the confusion by announcing to Hacker News that there are immutable norms of vulnerability disclosure that were broken in this case, especially when those supposed norms are false and most especially when they assert obligations researchers have to vendors.

Re:Our Interesting Call with CTS-Labs by ComputerGuru on Thursday March 15, 2018 @10:26PM (#16598123)
I don’t even have a problem with shorting. It’s fair game, and a company’s bug bounty should reflect what they stand to lose by not paying top dollar to preempt exactly that. Any talk about the company being “entitled” to anything is BS. If someone had a vulnerability that would get them access into anyone’s Dropbox as their IPO rolls out.. they’ve earned it.

I just think if that’s your plan, you best not be bluffing and had better have something really good up your sleeve. I do have a problem with overstating your case and spreading FUD to try to make a quick buck off of at best B+ attempt.