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.

Vulnerabilities / Threats

02:00 PM
Connect Directly
E-Mail vvv

Meltdown, Spectre Patches, Performance & My Neighbor's Sports Car

When a flaw in the engine of a data center server makes it run more like a Yugo than a Porsche, it's the lawyers who will benefit.

As I consider potential impacts from Meltdown and Spectre, what strikes me most is not the typical cybersecurity risks, reputational impacts, and operational hits. In the coming weeks and months, we will see lawsuits against the chip manufacturers, operating system providers, and OEM manufacturers whose devices house these chips and are the point of contact between the user and the chipset.

Surprisingly, it was my neighbors' sports car that led me to focus on the legal issues, not the industry evaluation and response to the chip vulnerability. When my neighbor was showing me his new Porsche, he made me think about engineering, performance, and speed, as well as the difference in our expectations when we make purchasing decisions. When a person buys a high-performance vehicle, he or she has certain expectations about speed, acceleration, and craftsmanship. For a sports car, the engine is the most critical part of the vehicle, and really it's what the car is built around.  

If I buy an $800,000 Porsche that is advertised to hit 60 mph in 2.2 seconds, then I expect it to perform reliably and consistently at this level. When I am advised the engine needs a system upgrade because of dangerous combustion timing and that upgrade decreases the performance of the vehicle by 30%, then I must question my purchase and whether the car has been negatively affected in a way that is irrecoverable and if it's no longer enjoyable.

Degraded Performance?
There are many similarities between my sports car analogy and the performance hits that may occur after applying patches or other firmware/system changes to mitigate the effects of Meltdown and Spectre on various processors. When consumers and businesses make purchasing decisions for computers, data center infrastructure, or cloud services, the operations teams focus on architecting systems to run in the most efficient manner, with the highest operational delivery specifications, and in a secure fashion.  

If processors that used to run, for example, on a laptop at 3.4GHz now run at 2.4GHz in bench tests, then the overall performance and/or productivity of the teams may be impacted or make for a less robust computing platform. If server architecture in a data center environment or cloud instance has been purchased and specified to run at a specific speed, transaction flow, or simultaneous user session speed and this is negatively affected, then there may be issues experienced by the end customer.  

Both of these scenarios of degraded processor speed may interfere with employees' ability to perform their job functions (think engineers, number crunching, and graphics), consumers' enjoyment of their newly delivered holiday gift, and production capabilities for websites that have high transaction volume and user utilization. In these cases, the processor still exists and is still working, but it has been degraded in a manner that may affect the overall value of the technology device, business function, or customer appreciation and continued use of the product or service.

Legal Issues
In the days ahead, CISOs will be examining the mitigating controls they can implement to decrease risks to their environments and customers. Chief operating officers will want to stay abreast of performance issues, operational degradations, and customer issues. Similarly, lawyers and contract and procurement officers will start to ask questions. Legal experts will seek information on what they contracted for in their purchase or lease of equipment or services and what they are now receiving in terms of promised speed and system utilization.

To the extent there is a delta between what was purchased and what is now in operation, lawyers may seek a reduction in price, new equipment, or indemnification for affected customers going forward. In many instances these discussions will be held quietly, but we can expect a new round of contract claims, tort claims, and—one of my favorite claims from the early days of CAN-SPAM litigation—trespass to chattels. This last claim is one that has been around for hundreds of years and appears in lawsuits when the property still exists but is being blocked from being used, impacted negatively, degraded, or otherwise unavailable. When property quality, condition, or value has been impaired, then one may have a claim for trespass to chattels.

We will have to examine more closely what the true performance effects are and whether or not they are material in the coming months. We will have to examine what types or remuneration might be possible if indeed the Porsche is now operating like a Yugo. But no matter what, we must patch and secure this fundamental building block in all our technological devices.

Related Content:


Dr. Chris Pierson is the founder & CEO of Binary Sun Cyber Risk Advisors. He is a globally recognized cybersecurity expert and entrepreneur who holds several cybersecurity patents. He serves on the Department of Homeland Security's Data Privacy & Integrity Advisory Committee ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
1/24/2018 | 10:02:47 PM
Re: Please don't feed the lawyers!
Equifax is a harder situation because (1) of who the customer is (NOT, in many cases, the people whose information was breached), (2) lack of regulation of the industry, and (3) lack of proof of any actual exploit or identity theft due to the breach in the vast majority of cases.

Meanwhile, FWIW, automakers themselves have already been sued for performance issues (in particular, mpg). I haven't been keeping good track, though, of how those cases have turned out.

(*Not legal advice. Not the formation, affirmation, or implication of an attorney-client relationship.)
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
1/24/2018 | 9:58:36 PM
Re: Please don't feed the lawyers!
Everybody loves to criticize attorneys until they need one.

(I remember being on a cruise where one of the couples seated at our nightly dinner table was a retired salesman and his wife. He asked me what I did for a living. I told him I was (among other things) an attorney. For the rest of the trip, he was vicious with "jokes" and other gibes about my profession and me personally (to the point that his wife was visibly embarrassed and tried to get him to stop). For my own part, I kept quiet and polite -- and afterwards laughed with my traveling companion about the stereotypes and barbs about "sleaziness" I could have thrown in his face for being a salesman.)


Funnily enough, I find that -- on the individual level (as opposed to business clients) -- in general, the worst clients with the worst cases tend to feel exceptionally strongly about their cause, while the best clients with the best cases feel that they're being a jerk by hiring a lawyer even though they got genuinely, completely, unlawfully screwed (and they wind up screwing themselves more by failing to talk to an attorney until well after their statute of limitations has run out).

I've seen exceptions, of course, but the point is that Chris is right in general principle. When you buy a product where you're given a guarantee as part of that sales process/agreement, you're not wrong to expect precisely what the salesman said (among other things, like, for instance, perhaps, that the thing works in general).

(*Not legal advice. Not the formation, affirmation, or implication of an attorney-client relationship.)
User Rank: Ninja
1/24/2018 | 8:23:28 AM
Re: Please don't feed the lawyers!
Agree!!!   The only group of people (read that sharks) who profit from these issues ARE LAWYERS.  
User Rank: Ninja
1/24/2018 | 12:53:42 AM
Please don't feed the lawyers!
Sorry, Chris: you'll have to wait for a future generation of lawyers - the current batch will all still be working the Equifax debacle when your neighbor's Porsche is a museum piece. 
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: What Virtual Reality phishing attacks will look like in 2030.
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
PUBLISHED: 2021-05-11
Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not perform a permission check in an HTTP endpoint, allowing with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
PUBLISHED: 2021-05-11
Jenkins P4 Plugin 1.11.4 and earlier does not perform permission checks in multiple HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified Perforce server using attacker-specified username and password.
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins P4 Plugin 1.11.4 and earlier allows attackers to connect to an attacker-specified Perforce server using attacker-specified username and password.
PUBLISHED: 2021-05-11
Jenkins Xcode integration Plugin 2.0.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.