21 ms·
Security Researchers Publish Ryzen Flaws, Gave AMD 24 Hours Prior Notice
- andrepd 9y ago>All of the exploits require elevated administrator access, with MasterKey going as far as a BIOS reflash on top of that. CTS-Labs goes on the offensive however, stating that it ‘raises concerning questions regarding security practices, auditing, and quality controls at AMD’, as well as saying that the ‘vulnerabilities amount to complete disregard of fundamental security principles’. This is very strong wording indeed, and one might have expected that they might have waited for an official response. Extremely fishy. 1-day notice? Such aggressive wording without even the chance for AMD to address the concerns?
- allthenews 9y agoI wonder if this is could be Intel up to its old tricks again.
- turbografx16 9y agoThis is so fishy to me, it's so unprofessional of a security researcher. My tinfoil hat is already rattling...
- tptacek 9y agoHave you done a lot of published security research?
- strictnein 9y agoNice non-sequitur. Somehow the limiting factor on the ability of someone to judge professionalism is the number of papers they've written?
- tptacek 9y agoNo, I'm just noticing again that people who don't don't do a lot of vulnerability research have a lot of interesting opinions about the professional norms of people who do that work. But you never know --- maybe they do a lot of research, in which case, yes, their opinion on security research norms is a lot more interesting to me.
- allthenews 9y agoI am not a security researcher, and I do not speak for the person you are replying to, but I do believe that Intel's documented history of unethical, anticompetitive practices against AMD, for example, deliberate compiler handicapping for non Intel CPUs[1], is enough evidence to establish at least some suspicion regarding these results, especially considering the short warning given to AMD before public disclosure. I also wonder, what is the purpose of such white hat operations if vulnerabilities are disclosed publicly without anywhere near adequate time for a fix? Isn't SOP to give more time before going public? 1.https://en.m.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Criticism https://en.m.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Criti...
- tptacek 9y agoI'm not arguing about Intel. If you think this is a giant conspiracy by Intel, more power to you --- I'm not engaging further on that.
- rainieri 9y agoMatasano and you got owned quite frequently back in the day. Should be judge you or your company or your opinions based on that too?
- ilovecars2 9y agoWhat’s the background here?
- tptacek 9y ago
- deleted 9y ago[deleted]
- simias 9y agoYeah it's suspicious. The website[1] has many fancy infographics, marketable names and fear mongering but you have to dig into the whitepaper[2] to find any details about the actual vulnerabilities. And even then it starts only on page 8 of 20 and you discover that it's vulnerabilities targeting the secure boot infrastructure and you need local admin to exploit them. It's not good but it's not a new Spectre or Meltdown. If I was the tinfoil hat type I'd guess that Intel is trying to spread FUD but maybe it's just security researchers trying to generate a bit of buzz for their company at the expense of AMD. [1] https://www.amdflaws.com/ https://www.amdflaws.com/ [2] https://safefirmware.com/amdflaws_whitepaper.pdf https://safefirmware.com/amdflaws_whitepaper.pdf
- dnautics 9y agoIt's possibly even more nefarious than that: 1) execute a series of puts on AMD, 2) release exploit 3) profit. If you execute an option with a far time horizon and give the company enough time to mitigate their vulns, then I think this is not an irresponsible thing to do (as it incentivises the company to actually do something), but with 24 hours notice...
- mizzack 9y agoSeeing as CTS-Lab's CFO also founded a hedge fund you're probably on the right track. >Yaron co-founded CTS-Labs in 2017, and previously served as an intelligence analyst in the Israeli Intelligence Corps Unit 8200. He is also the founder and Managing Director of NineWells Capital, a hedge fund that invests in public equities internationally. He holds a B.A. and M.A. from Yale University.
- tptacek 9y agoIndependent researchers don't owe AMD a chance to address anything. They bought the chips on the open market where AMD makes them available, and then used their own time and materials to conduct their own research. Their work product is their own, and AMD has no claim to it. There are, as I see it, two rational, coherent ways to be outraged about this story: 1. The vulnerabilities are fabricated and the report is fraudulent, in which case, by all means, slag the researchers. 2. The vulnerabilities are real, in which case. AMD is an 11 billion dollar company that got outmaneuvered by what appears to be 4 dudes in a basement.
- webbles 9y agoGo fuck yourself. There are plenty of ways to be outraged by the actions of these "independent reseachers." How about 1. Irresponsible disclosure affecting end users. 2. Shady trading practices of their hedge fund CFO. Just to name 2. You are a fucking retard, and your obvious anti-AMD bias is showing.
- sctb 9y agoWe've banned this account. If you would like to post civilly and substantively you're welcome to email us at hn@ycombinator.com and we'll unban it if we believe you will. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- travmatt 9y agoI wonder if the unusually short disclosure process was related to their disclosure of related financial interests. If it was, it’d seem that this research was in support of a financial play similar to how Muddy Waters shorted St. Jude Medical on the basis of insecure medical devices. That would appear to be a legitimate strategy, but if the market didn’t punish Intel for their processor vulnerabilities it seems likely they’d react similarly here and the research would fail to move the stock price in any significant way.
- deleted 9y ago[deleted]
- 9y ago
- Digital-Citizen 9y ago> 1-day notice? Such aggressive wording without even the chance for AMD to address the concerns? Are the reporting parties under any obligation to give AMD notice? Behaving according to AMD's wishes is not an obligation. Businesses will be the first to tell you that agreements and laws form obligations, not what someone perceives as a nice thing to do. If not, then you're reacting to a distraction, a detail that doesn't matter: how the corporate-friendly tech press is trying to shift blame away from the party that either sold CPUs with bugs in them (mistakes happen, and this is unfortunate) or distributed nonfree (proprietary, user-subjugating) software which also happens to contain insecurities (a malicious and unjust way to distribute software).
- jaxtellerSoA 9y agoYou mean to tell me my machine can be exploited if I let someone do one of the following. 1. Flash the BIOS 2. Have admin access Holy shit, this calls for a full fledged panic! I am very disappointed anandtech.com even bothered to give this smear campaign the time of day. If someone can flash your BIOS or has admin access then you already have way bigger problems.
- kbenson 9y agoCTS-Labs is very forthright with its statement, having seemingly pre-briefed some press at the same time it was notifying AMD, and directs questions to its PR firm. The full whitepaper can be seen here, at safefirmware.com, a website registered on 6/9 with no home page and seemingly no link to CTS-Labs. Something doesn't quite add up here. Anandtech is reporting on the situation more than the flaws. That does require covering what the flaws are though. Not covering it at all isn't exactly performing good journalism either.
- volgo 9y agoPeople here seems to be mentioning short sellers being connected to this research as if there's some sinister collusion going on. This is the entire point of short selling, and SEC encourages this type of activism. It allows people who can provide expert knowledge to profit off a trade if it can reveal damaging and legitimate information about a company For example, a short seller last year revealed (through extensive research), that Valeant Pharmaceuticals was stuffing its channels and faking its finances. He placed a huge sort sell and went public with the damaging info - tanking the stock from $270 to $12 and made a ton of profit off of it: https://www.nytimes.com/2017/06/08/magazine/the-bounty-hunte.. https://www.nytimes.com/2017/06/08/magazine/the-bounty-hunte.... Without this incentive, why would anyone bother to reveal damaging info? You're placing your self as a target with no reward. The payment is the natural balance of the market. So yes, this research firm is connected w a hedge fund, and they have a very vested interest. But that doesn't make their claim untrue
- jadedhacker 9y agoI'm not saying it was them, but I wouldn't be surprised if Intel was trying to recover its reputational damage by hiring ppl to heavily research breaks in AMD chips to even the reputational playing field. They're the ones that stand to gain the most from this legal but shady tactic and have been reportedly scared of losing their long held market dominance in desktops and servers. Iirc AMD wasn't vulnerable to Meltdown which I speculate changed the market calculus in ways detrimental to Intel that both companies would be well aware of. Interestingly, you'll note that the researchers claim public interest as their reason for non-standard practices, but then later it is revealed you need admin privileges to exploit them. The rhetoric the researchers use is inflammatory and staged in a media savvy way like a PR campaign. This is a totally evidence free assertion and I'm not an infosec person (and am therefore happy to be set straight by experts) but I'll be happy to crack open the popcorn if something interesting is revealed a few years down the line.
- fulafel 9y agoDoes this enable auditing of the psp, or replacing the sw with trusted code?
- sneak 9y ago> AMD is in the process of responding to the claims, but was only given 24 hours of notice rather than the typical 90 days for standard vulnerability disclosure. No official reason was given for the shortened time. 90 days is not a standard. Nothing was shortened. People are allowed to publish their research whenever they like. Vendor advance notification is optional. Full, immediate disclosure is responsible.
- jamespo 9y ago"Full, immediate disclosure is responsible." says who?
- tedunangst 9y agoMe.
- tedunangst 9y agoNot allowed to say that here.
- strictnein 9y agoYou're allowed to say plenty of wrongheaded things here and elsewhere on the Internet.
- tetromino_ 9y agoA few (far from all!) software vendors realistically might be able to respond and issue a patch in 24 hours. But a hardware vendor cannot. See Intel's recent debacle [1] for what happens when a silicon vendor rushes a security fix out of the door without going through a proper multi-week QA cycle. [1] https://arstechnica.com/gadgets/2018/01/good-newsbad-news-in-quest-to-get-meltdown-and-spectre-patched/ https://arstechnica.com/gadgets/2018/01/good-newsbad-news-in...
- wtallis 9y ago> Full, immediate disclosure is responsible. Hiring a PR firm before disclosing to the vendor is not responsible. Briefing select press before disclosing to the vendor is not responsible.
- chx 9y agoDid anyone verify any of these? The whole thing reeks.
- cookiecaper 9y agoGood question. They call the "MASTERKEY attack" that requires a reflashed BIOS "remotely exploitable" because on some systems, the BIOS can be flashed from the OS. They then speculate "On motherboards where re-flashing is not possible because it has been blocked, or because BIOS updates must be encapsulated and digitally signed by an OEM-specific digital signature, we suspect an attacker could occasionally still succeed in re-flashing the BIOS." Page 9 in the PDF. I'm not a professional security researcher but this is looking pretty darn flimsy. I also don't see any proof of concept code anywhere -- the "whitepaper" seems to just claim these things exist with very little mention of how to exploit them. Compare against Meltdown/Spectre, which was highly technical and had lots of PoC code. This just says "Upload malware to the processor" without further comment. I'm not saying they didn't find anything, but whatever they found, they've hardly disclosed it.
- Sephr 9y agohttps://twitter.com/dguido/status/973628511515750400 https://twitter.com/dguido/status/973628511515750400
- robert_foss 9y ago24hrs notice is unheard of. Who works for CTS-Labs? Attaching your name to a company like that should disqualify you from any future jobs in the security space.
- samfriedman 9y agoThey seem to have 3 employees on LinkedIn. The co-founders, at least, seem to have listed experience in security & security consulting.
- coldacid 9y agoAnd (financial) securit_ies_. Follow the money.
- deleted 9y ago[deleted]
- tptacek 9y agoWho do you think you speak for? Assuming the vulnerabilities aren't fabricated --- it's happened before with other companies --- attaching your name to that white paper probably guarantees you lifetime employment in security research. "Unheard of"? People have dropped serious vulnerabilities with _zero_ warning before.
- gshulegaard 9y agoPerhaps this is my ignorance, but I was under the impression that security disclosures are usually tightly coordinated to minimize exposure of innocent users. > "Unheard of"? People have dropped serious vulnerabilities with _zero_ warning before. Could you point me to an example of a zero warning disclosure that exposed a large amount of users without first attempting to coordinate with the responsible party?
- tptacek 9y agoSome researchers coordinate, some researchers don't. For a project originally organized around the principle of getting not just research results but functioning exploit code deployed regardless of vendor preparedness, look no further than Metasploit.
- yAnonymous 9y agoThis is FUD. The original post was flagged, because the domain and website are far from trustworthy. Technically, the accusations seem to be more of a joke. Hello, Intel?
- Sephr 9y agoDan Guido is backing up their claims.
- stevespang 9y agoHow much money did Dan accept under the table, eh ?
- dabeledo 9y ago"Although we have a good faith belief in our analysis and believe it to be objective and unbiased, you are advised that we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports." from the disclaimer
- bhouston 9y agoWhy does it say this on the disclaimer: "...we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports." Are they shorting AMD? https://amdflaws.com/disclaimer.html https://amdflaws.com/disclaimer.html
- vesrah 9y agohttps://amdflaws.com/disclaimer.html https://amdflaws.com/disclaimer.html "you are advised that we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports"
- nodesocket 9y agoAlmost always these types of security incidents and breaches NEVER move stock prices negatively because frankly they don't impact business. $AMD is currently trading up 3.5% as of writing this. :-)
- matt4077 9y agoThat’s... sort of ok? It’s not perfect, but it opens up another avenue to finance security audits besides selling exploits to intelligence services, attacking end-users (both worse), and collecting rewards from the companies (better).
- zitterbewegung 9y agoAMD's stock was negative multiple times today ($11.38 on March 13, 2018 10AM,and at 12Noon on NASDAQ). Shorting the stock would be an obvious play. I have heard of people thinking about trading on security flaws in products but never seen it done in real life.
- swyx 9y agoyes and its $11.77 now (up 2%) this is not in the same league but i recall AMD/INTC also traded up on the spectre/meltdown debate. a lot of insecure chips ironically leads to a lot of demand for new secure-er chips.
- this_user 9y agoThere is also some questionable research group involved in all of this: https://viceroyresearch.org/2018/03/13/amd-the-obituary/ https://viceroyresearch.org/2018/03/13/amd-the-obituary/ It's not uncommon for short sellers to take a position first before releasing a report like this to drive the stock lower. Of course, there are legitimate groups that, in the past, have unearthed real issues and corporate misconduct, but there are also questionable groups that will release reports with little to no substance. This case certainly does looks dubious, but I'd like to see an assessment by reputable security expert.
- bhouston 9y agoDUPE of https://news.ycombinator.com/item?id=16576516 https://news.ycombinator.com/item?id=16576516
- fancyfredbot 9y agoOne of the co-founders runs a hedge fund. The website's disclaimer says "you are advised that we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports". Just sayin.
- youseecomrade 9y agohttps://www.reddit.com/r/Amd/comments/84510f/call_to_action_amd_share_price_manipulation_sec/ https://www.reddit.com/r/Amd/comments/84510f/call_to_action_...
- notacoward 9y ago24 hours means they don't deserve to be called security researchers. They're exploit creators. Given the material effect this would have on AMD's stock, one might also reasonably speculate about their financial interests.
- strictnein 9y agoThis. Especially with the disclaimer that others have noted: > "we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports"
- tptacek 9y agoOne difference between security researchers and "exploit creators", which is a term I think you just made up, is that exploit creators presumably release exploits. Don't tell HD Moore or the Metapsloit team about this, though. They may cry themselves to sleep tonight.
- notacoward 9y agoCreation and release are two different things. They have created the exploits, or else AMD wouldn't be taking them seriously. They have also contributed more to the re-creation of those exploits by others than they have to security. So you can quibble over whether others use the exact jargon that you would have, but that doesn't change the underlying reality.
- tptacek 9y agoEvery security researcher creates exploits, so I'm not really sure what the distinction you're trying to make is.
- unethical_ban 9y agoVulnerability and Exploit are different.
- 9y ago
- paulie_a 9y ago"One hit wonder" security firm is trying to make a name for itself.
- peterpan31 9y agoScammy site, see: https://news.ycombinator.com/item?id=16576516 https://news.ycombinator.com/item?id=16576516
- rdl 9y agoIf the vulnerabilities were real, I'd have no problem with a company using it to promote themselves, trade and talk their book, etc. The issue here is the vulnerabilities are very overhyped (some are fundamental things like "if you reflash your BIOS with evil, you're screwed", some just make local root access more persistent, etc. The problem with something like TRO LLC is that markets don't move on security info.
- bsilvereagle 9y agoI think the economics/ethics of the researchers are overshadowing something big: "RYZENFALL allows malicious code to take complete control over the AMD Secure Processor." "Multiple vulnerabilities in AMD Secure Processor firmware allow attackers to infiltrate the Secure Processor." If this is legitimate, this is huge! The PSP could potentially be disabled! Very little work has gone into handicapping the PSP compared to the IME.
- kiddico 9y agoWell there was a big community push a while ago to have the new AMD cpus have an option to disable the PSP. I'm gonna wishfully think this was intentionally done to allow us to disable the PSP.
- fencepost 9y agoIs it wrong that my immediate reaction to that was "Wait, isn't/wasn't the PSP a portable? Did they actually use x86/x64 AMD processors in those? How?? AMD's traditionally been poor on power management!"
- kingwill101 9y agosomething smells fishy... y 24hrs warning? whatever happened to the usual 90 days disclosure?
- tcoppi 9y agoIf anyone trades options, the IV on options expiring in March on AMD went up significantly last week with no apparent news, probably because of these guys.
- AstralStorm 9y agoThe upside of this is that most of these vulns are ineffective after disabling AMD "Secure" Processor at boot which is now an option in most firmware. Without breaking manufactures firmware upgrade key you cannot execute the first one to toggle the settings. The interesting one is against Promontory. It still requires VM host access to exploit so the impact is limited.
- slizard 9y agoWild guess / conspiracy theory: Intel, afraid of the damage to their image just made worse by diminished performance advantage compared to AMD )due to Meltdown), fearing long-term market loss, quickly found ways to tackle the issue by, instead of pedaling to regain trust, damaging a competitor's image. It seems like a reasonable long game to support and perhaps steer the disclosure of AMD vulnerabilities that CTS-labs had been investigating. Or maybe is was Intel investigating themselves, had some cards up their sleeves, but needed some other entity to do the public disclosure. Other theories discussed here seem less far-fetched than the above, but in any case, it does smell funny.
- HelloNurse 9y agoMy guess is that some researcher found something and decided to maximize profits, scraping the bottom of the barrel of quasi-vulnerabilities, creatively exaggerating, and bringing in the lawyers, the financiers and the PR weasels needed to throw a scary web site and a misleading "white paper" at AMD. We'll see what CTS works on next.
- eganist 9y agoLegal question: Insider trading claims might be difficult since you can claim the vulnerabilities were public knowledge waiting to be discovered, but... Can you trade on knowing the security disclosure timeline prior to your publication of the vulnerability? That would seem to be insider knowledge until AMD authorizes publication. E.g. I've got knowledge that AMD likely wouldn't be able to fix the flaws prior to my disclosure. That knowledge would inherently be non-public. Thoughts? Disclosure: I've been long AMD for a while.
- Sephr 9y ago> until AMD authorizes publication AMD doesn't have the power to prevent publication of research from third party researchers that haven't entered in an agreement with them. This definitely isn't insider trading.
- eganist 9y ago> AMD doesn't have the power to prevent publication of research from third party researchers that haven't entered in an agreement with them. This definitely isn't insider trading. Correct, though this assumes AMD has yet to reply. If AMD did reply after the initial disclosure and before any trades were made, then the order of events which may warrant such a look would be: - Private Disclosure made. - AMD replies privately with anything substantive. This could include a timeline, or even an indication that a fix may take a while. - Trades made. - Public disclosure made. Should events follow this sequence, trades made would have been informed by private knowledge from AMD that had yet to be released. I'm not saying this is how it played out, but if it did, I'd suspect some amount of legal exposure.
- Sephr 9y ago> AMD replies privately Their replies are only private if the discloser keeps them private. The discloser is free to publish their correspondences with AMD which may include a timeline. Regardless, this entire publication can happen without once talking to AMD. There is no need to notify or correspond with AMD in order to publish the security research and short AMD's stock.
- ilkkao 9y agoLinus' reaction: https://plus.google.com/+LinusTorvalds/posts/PeFp4zYWY46 https://plus.google.com/+LinusTorvalds/posts/PeFp4zYWY46
- d33 9y agoIt's quite unsettling that Linus thinks as much of security in general, given that he maintains a kernel and he's responsible for accepting its security modules that are next to unusable because of their complexity. Could his general disbelief lead to a (kind of) dismissive attitude in this respect? Keep in mind he's the one that would never properly disclose of a security fix - instead of saying which problem is fixed, the general approach is to just publish a new kernel minor release and say "some security bugs are fixed, go figure".
- tptacek 9y agoPeople who work in vulnerability research generally just point and laugh at him. His opinion on this doesn't matter.
- zokula 9y agoAnd the people who focus on real security point and laugh at the so called "vulnerability research engineers", and agree with Linus point.
- d33 9y agoI'll bite. What's "real security"?
- lawnchair_larry 9y agoNo, that isn’t a thing
- adtac 9y agoI found this on /r/AMD haha: https://i.imgur.com/OkWlIxA.jpg https://i.imgur.com/OkWlIxA.jpg
- deleted 9y ago[deleted]
- bitL 9y agoI'll still buy Threadripper/EPYC. There is nothing else on the market that is comparable for my needs.
- pbhjpbhj 9y agoOne thing that does strike me is that, after the Intel Co. situation, giving only a little notice prevents execs from being able to short their own stock on the vuln. Is this confirmed yet?
- otherme32 9y agoIt seems to me a pretty mild security flaw one that requires local root privileges or even reflashing the BIOS to be exploited. I cannot think of a real world scenario where this can be a problem.
- goodmachine 9y agoAmazing coincidence! On the very same day this information came out, 'Viceroy Research Group' managed to release a 33-page 'analysis' of these results. With illustrations. Headline: >We believe AMD is worth $0.00 and will have no choice but to file for Chapter 11 (Bankruptcy) in order to effectively deal with the repercussions of recent discoveries. Viceroy Research lists no employees or contact address, but it appears they are not a crack team of hardworking & incisive business analysts, but two Australian teenagers and a former UK child social worker, struck off in 2014 for misconduct. They have previous form in producing or plugging short-call stories (quite effectively), and latterly investigated by South African media for similar shady business. https://www.moneyweb.co.za/in-depth/investigations/viceroy-unmasked/ https://www.moneyweb.co.za/in-depth/investigations/viceroy-u... It took very little internet sleuthing to find this stuff out. None of the tech press bothered to do so. Disclaimer: I have no position in AMD. Edit: link to Viceroy https://viceroyresearch.org/ https://viceroyresearch.org/
- paulmd 9y agoA security researcher claims to have access to the full (non-public) technical report as well as PoC exploits for it. He says they're legit, and they are flaws, not just "you can do admin things with an admin password". https://twitter.com/dguido/status/973628511515750400 https://twitter.com/dguido/status/973628511515750400 Sounds like the capabilities include the ability to jump outside a VM sandbox, take over the PSP, and pivot to the firmware or BIOS exploits. https://www.techpowerup.com/242328/13-major-vulnerabilities-discovered-in-amd-zen-architecture-including-backdoors https://www.techpowerup.com/242328/13-major-vulnerabilities-...
- pishpash 9y agoHow do we know this guy's not a conspirator?
- paulmd 9y agoTrack record of research/publications in the field? https://www.trailofbits.com/research-and-development/published-research/ https://www.trailofbits.com/research-and-development/publish... Ian Cutress of Anandtech appears to be quasi-vouching for Dan Guido. Ian is also interviewing CTS Labs tomorrow morning, and looking for questions. https://twitter.com/IanCutress/status/973678700687450113 https://twitter.com/IanCutress/status/973678700687450113 https://twitter.com/IanCutress/status/973697525071994880 https://twitter.com/IanCutress/status/973697525071994880
- deleted 9y ago[deleted]
- mjevans 9y agoSince all of this seems to be related to "Secure Boot" and other DRM related crap, can we please just have the option of booting with minimal firmware support, no hidden code, and go for a completely open, community maintained, and audit-able by /anyone/ infrastructure? No, I don't want HDCP or any similar crap; let me run my servers and desktops in secure mode.
- pishpash 9y agoNo reaction from the stock market. I'm not interested.
- roselan 9y agoWhat shocks me is that most mainstream media report it. It's on top of techmeme, and all major names are linked. sigh.
- pishpash 9y agoI lol'ed at this in the "whitepaper" for a potential impact of a claimed vulnerability: Physical damage to hardware (SPI flash wear-out, etc.) Reminds me of little kids trying to fill out their 200-word essays.
- mark-r 9y agoApparently all these can only be exploited if you already have administrator privileges. Raymond Chen calls that "being on the other side of the airtight hatchway" and has written about it numerous times. https://blogs.msdn.microsoft.com/oldnewthing/20060508-22/?p=31283 https://blogs.msdn.microsoft.com/oldnewthing/20060508-22/?p=...
- defmer 9y agoThis is just Intel trying to muddy the AMD waters
- stevespang 9y agoThis has all the signs of a bonafide smear job, Intel has a huge presence in Israel, lot's of investments there. Wouldn't take much to use stealth proxy operatives to carry out such a smear, and guess who benefits the most from a smear of AMD ?
- NKCSS 9y agoThe 24h disclosure should not be too much of a problem, since they state: > "we are letting the public know of these flaws but we are not putting out technical details and have no intention of putting out technical details, ever" It's always a risk, because now people know where to look to recreate it themselves, it's not like this is a full-disclosure release where you're SOL as a manufacturer and have to race rampant public exploitation.