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.

Database Security
Authentication
Mobile
Privacy
Compliance
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Intel Says to Stop Applying Problematic Spectre, Meltdown Patch
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
1/24/2018 | 9:48:30 PM
Re: What's the score?
@Brian: Well, sure, technically, it is the awareness of an issue that presents a problem more directly than the problem itself. Scrodinger's Vulnerability, I suppose.

But, of course, for all anyone knows, the vulnerability has already been exploited in the wild (and, if so, very possibly even by nation-state actors, who would probably be the best poised to have known about the vulnerability and have done so -- especially without you finding out about it).

Sure, good coordination has to go into vulnerabilty announcements and patch processes, but because this particular vulnerability is so disastrous and severe, it would be hard for much of the population to not take a Chicken Little approach here. It's a pretty bad vulnerability.
BrianN060
50%
50%
BrianN060,
 User Rank: Ninja
1/24/2018 | 12:38:29 AM
Re: What's the score?
@Joe: "The chaos stems more from the fact of the existence of the vulnerability." From the existence, or the manner of itheir being made public?  The vulnerabilities (or the design decisions which would become vulnerabilities once cyber-technologies and use patterns would make them such), existed for decades.  Not being an insider, I only became aware of the issue with the media disclosure (and via sites like DR).  That's when the chaos began.

I wasn't talking about balancing likelihood against severity (akin to gambling, in my opinion), but the realized cost of the uncoordinated efforts at mitigation, against as yet unobserved exploitation.  It didn't have to play out like this. 

To your other points: agreed - the bungled and disjointed patches and updates are unfortunate, for the reasons you mentioned. 

Your comments @Ryan: also agreed - a holistic approach is required; especially as attacks become more sophisticated and use multiple vectors. 
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
1/23/2018 | 11:10:08 PM
Patches beget patches
This is grossly unfortunate because the very reason many people are wary of updates that are non-security or partial-security related is because of severe bugs that are usually hiding in a rushed rollout (q.v. iOS). To see this in the strictly security patch context where the severity is so high is particularly disheartening and may cause people to take the issue less seriously, I wonder.
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
1/23/2018 | 11:08:16 PM
Re: What's the score?
@Ryan: Yeah, but the thing is that many attacks really are "insider attacks" because even so many "outsider" attacks require compromising "insider" credentials. So it's a matter of treating this holistically and in depth as opposed to an "M&M security" approach (hard on the outside, soft in the middle).
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
1/23/2018 | 11:06:31 PM
Re: What's the score?
@Brian: The chaos stems more from the fact of the existence of the vulnerability. I'm not really sure that the question is well-founded given that the flaw is desperately serious.

Sure, risk management is all about assessing likelihood just as well as severity, but in this case severity is so high that it overshadows any probability rating that any accepted threat model could slap on it.
RyanSepe
50%
50%
RyanSepe,
 User Rank: Ninja
1/23/2018 | 8:20:21 AM
Re: What's the score?
That's a good question that I would be interested in as well. Although this vulnerability affects a majority of devices the greatest risk, outside of affected DMZ devices, are users already inside of your network. Essentially it allows for persistent listeners to take advantage of an easy exploit when it may have taken them a while to figure out how to traverse the network.
BrianN060
50%
50%
BrianN060,
 User Rank: Ninja
1/23/2018 | 1:10:27 AM
What's the score?
The DR staff are better informed than I am; but has any of the cost and chaos of Meltdown/Spectre mitigation yet been shown to have thwarted a single attempted explotation?  Put another way, have those that haven't bothered to lift a finger to prevent M/S exploitation paid the price for their indifference?  One more question: how would you rate the handling of the M/S issue, from first discovery of the vulnerabilities, to the press leaks, public announcement, vendor reaction and community response - so far?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.