Hi folks,
Here we are with another issue!
It's weeks like these that I'm happy that I moved the "Breaches and leaks" section to the bottom, because it's a looong one this week. Otherwise I'd feel obligated to trim it down. Now you can browse at your leisure to see if anything jumps out at you :-)
Enjoy the read, and have a wonderful weekend!
Look, I'll be honest. Whenever these CPU vulnerabilities are reported my head starts spinning by the time I get to the second paragraph. But I'll try to interpret it as best I can.
As I understand it, it allows attackers to revert cached VM memory to a previous state, thereby finding previously authenticated sessions or recovering private keys that they can use to get themselves access or escalate privileges. But the statement of AMD does say it requires a malicious hypervisor? If your hypervisor is malicious, I'd think you have bigger problems. Still, it sounds like a clever hack.
Another CPU vulnerability, this time for Intel. It ... has something to do with prefixes.
From the article:
"Under certain microarchitectural conditions, Intel has identified cases where execution of an instruction (REP MOVSB) encoded with a redundant REX prefix may result in unpredictable system behavior resulting in a system crash/hang, or, in some limited scenarios, may allow escalation of privilege (EoP) from CPL3 to CPL0".
Yep.
I'll move on the words of comfort that we all seek:
While it might be possible to achieve privilege escalation with this vulnerability, that hasn't happened yet, although it can cause a DoS. Still, Intel does not expect this issue to be encountered in the real world, but just in case there is a microcode update available.
Citrix Hypervisor is also affected, they released a patch as well: link.