Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

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   >   >>


Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: I think the boss is bing watching '70s TV shows again!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5680
PUBLISHED: 2020-12-03
Improper input validation vulnerability in EC-CUBE versions from 3.0.5 to 3.0.18 allows a remote attacker to cause a denial-of-service (DoS) condition via unspecified vector.
CVE-2020-5638
PUBLISHED: 2020-12-03
Cross-site scripting vulnerability in desknet's NEO (desknet's NEO Small License V5.5 R1.5 and earlier, and desknet's NEO Enterprise License V5.5 R1.5 and earlier) allows remote attackers to inject arbitrary script via unspecified vectors.
CVE-2020-5676
PUBLISHED: 2020-12-03
GROWI v4.1.3 and earlier allow remote attackers to obtain information which is not allowed to access via unspecified vectors.
CVE-2020-5677
PUBLISHED: 2020-12-03
Reflected cross-site scripting vulnerability in GROWI v4.0.0 and earlier allows remote attackers to inject arbitrary script via unspecified vectors.
CVE-2020-5678
PUBLISHED: 2020-12-03
Stored cross-site scripting vulnerability in GROWI v3.8.1 and earlier allows remote attackers to inject arbitrary script via unspecified vectors.