So is this fixed at the OS level, ie a Windows Update, my laptop manufacturer just pointed me towards https://meltdownattack.com
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
According to the VMware notification sent yesterday, Workstation 14.x isn't vulnerable.
TBH i cant see the majority of pcs getting a bios fix Unless your on a reasonably recent chipset
We have a bunch of vms including database servers in test environments where security is no issue but performance is.
Unless the testing is purely functional, it should really be run in an environment that's representative of production - i.e. with the patch enabled. It'll be no good proving performance in test only for it to be slower when released to live.
I realise I've made a lot of assumptions above
The answer to that is no (and this doesn't relate to the ME vulnerabilities discovered last year), the MS patch isn't enough to fully mitigate the issues.
More information can be found here for servers - https://support.microsoft.com/en-us...-to-protect-against-the-speculative-execution
and here for the desktop OS - https://support.microsoft.com/en-us...ive-execution-side-channel-vulnerabilities-in
Main things to note, you need an AV that is adding the reg-key for the patch to be installed. If you're on a Windows server OS then you will also need to add reg-keys AFTER the patch install to enable the fix.
There is also a powershell module that you can install to verify the status of the machine.
Because you need a BIOS update / CPU microcode patch to fix the security issues. If your motherboard maker hasn't released an update in the last 24 hours then wait until they do and update as soon as possible. These security issues can't just be fixed by an operating system patch, you need a BIOS update / CPU microcode fix.
So is this fixed at the OS level, ie a Windows Update, my laptop manufacturer just pointed me towards https://meltdownattack.com
How do you know there's no attack?For most home users, why the panic this is just a threat no certain attack.
I agree, I'm running a really old chipset and CPU what are the chances people like us get a bios update?, and if we don't do we just throw our gear into the bin?
There are 2 separate vulnerabilities (Meltdown and Spectre), however there are 2 different exploits discovered against Spectre so far.
Meltdown: affects Intel CPUs and one Arm core – the yet-to-ship Cortex-A75 - this can be mitigated via OS updates (of which MS have released updates, and Linux updates are available)
Spectre variant 2: affects Intel and Arm cores. Pre-Skylake CPUs need a microcode update (so potentially a BIOS update) to help mitigate this. OS Kernels and hypervisors (i.e. VMs) also need patching.
Spectre variant 1: affects both Intel and AMD CPUs, and certain ARM cores. It is difficult to exploit as relies on timing based attacks, but some measures are being taking by Software developers (e.g. Browsers already have a patch to make timers less accurate)
Paraphrased somewhat from:
http://www.theregister.co.uk/2018/01/05/spectre_flaws_explained/
Thanks.
So my i5-7200U what will that require.
I think you're basically safe in that scenario.So, how exactly is this exploited? For example; If you're running a server and not installing any new software or browsing any websites, how can an attacker possibly exploit the meltdown/spectre vulns?
So, how exactly is this exploited? For example; If you're running a server and not installing any new software or browsing any websites, how can an attacker possibly exploit the meltdown/spectre vulns?
I think you're basically safe in that scenario.
On a standalone server with no Virtualisation, then risk is low - you would need some other exploit or user intervention to get into a situation where this would be exploitable.
However on VM's and similar this potentially allows data to "leak" between VMs - hence why Cloud providers are understandably worried.
For home users, the risk is that information can potentially be "leaked" between sandboxed apps (e.g. browser tabs), e.g. a maliciously coded advert etc in one tab, could potentially read information from a 2nd tab.
Although exploits are difficult to produce and not necessarily in the wild - now the vulnerability is public knowledge, it's likely that more evolved exploits will come.