Comments
Microsoft Issues Emergency Patch to Disable Intel's Broken Spectre Fix
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
1/30/2018 | 7:42:22 PM
Re: A question for DR
@Dr.T. "...Hopefully these variants will end soon."  I don't see how they could - but then I'm not on conference calls with the big players.  Maybe they have, or can, come to an agreed roadmap of mitigation waypoints, towards a solution.  If so, that would be a real achievement.  Without that, whatever one does will tilt the table for the others.  That goes for chip/OS and OS/ISVs (so chip/ISVs, as well).  With the pressure (public, political, contractual), on all of them, I imagine it's like playing the Twister game paced to a Bach Fugue. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:34:02 PM
Re: A question for DR
That is a very real possibility, and indeed it does question how Intel (and its competitors) can better build on-chip security, Intel has mot steak in this than others so it would be more important for them to get it right.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:32:39 PM
Re: A question for DR
Just wondering if on-chip security was really the best path, to begin with? It's like designing a hammer that will prevent you from hitting That is a real good question to ask. Any flow in HW would be hard to fix, maybe we need to evaluate options for HW independence.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:29:42 PM
Re: A question for DR
what happens when a new hardware vulnerability is discovered in those? That will be a real blow to intel, they my even go out of business for that.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:26:34 PM
Re: A question for DR
How are things going at your organization? We are mainly applying patches released by Microsoft. Not much other options.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:25:30 PM
Re: A question for DR
The real fix to these flaws is a new generation of microprocessors, which will likely take years for most organizations to adopt. That makes sense, I am also wondering if there is way to fix exiting CPUs for new devices.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:23:43 PM
Re: A question for DR
The patches don't really fix anything--they just mitigate exploits- I think that is why we need to go to a real solution, performance hit is not really acceptable.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:22:06 PM
Re: A question for DR
The patches/updates were obviously rushed without time to properly vet and test them. That makes sense. They would still see problems when they deploy it to mass market.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:20:33 PM
Re: A question for DR
Would the last few weeks of chaos been avoided, if the confidentially informed vendors had more time before public disclosure? I hear you, I would say it would be the same, they would not take action until last minute.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/30/2018 | 7:19:22 PM
Re: A question for DR
Once we learned that underlying vulnerability was multi-chip-vendor (so multi-OS and Applications), we knew a long series of mitigation and fix iterations was inevitable. That makes sense. Hopefully these variants will end soon.
Page 1 / 2   >   >>


Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Data Privacy Careers Are Helping to Close the IT Gender Gap
Dana Simberkoff, Chief Compliance and Risk Management Officer, AvePoint, Inc,  8/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15601
PUBLISHED: 2018-08-21
apps/filemanager/handlers/upload/drop.php in Elefant CMS 2.0.3 performs a urldecode step too late in the "Cannot upload executable files" protection mechanism.
CVE-2018-15603
PUBLISHED: 2018-08-21
An issue was discovered in Victor CMS through 2018-05-10. There is XSS via the Author field of the "Leave a Comment" screen.
CVE-2018-15598
PUBLISHED: 2018-08-21
Containous Traefik 1.6.x before 1.6.6, when --api is used, exposes the configuration and secret if authentication is missing and the API's port is publicly reachable.
CVE-2018-15599
PUBLISHED: 2018-08-21
The recv_msg_userauth_request function in svr-auth.c in Dropbear through 2018.76 is prone to a user enumeration vulnerability because username validity affects how fields in SSH_MSG_USERAUTH messages are handled, a similar issue to CVE-2018-15473 in an unrelated codebase.
CVE-2018-0501
PUBLISHED: 2018-08-21
The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.