this post was submitted on 18 May 2024
339 points (92.9% liked)

Weird News - Things that make you go 'hmmm'

921 readers
48 users here now

Rules:

  1. News must be from a reliable source. No tabloids or sensationalism, please.

  2. Try to keep it safe for work. Contact a moderator before posting if you have any doubts.

  3. Titles of articles must remain unchanged; however extraneous information like "Watch:" or "Look:" can be removed. Titles with trailing, non-relevant information can also be edited so long as the headline's intent remains intact.

  4. Be nice. If you've got nothing positive to say, don't say it.

Violators will be banned at mod's discretion.

Communities We Like:

-Not the Onion

-And finally...

founded 1 year ago
MODERATORS
[email protected]
[email protected]
339
A Windows XP machine's life expectancy in 2024 seems to be about 10 minutes before even just an idle net connection renders it a trojan-riddled zombie PC (www.pcgamer.com)
submitted 6 months ago by [email protected] to c/[email protected]
56 comments fedilink hide all child comments
 

Just a fun, somewhat terrifying read

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 6 months ago (1 children)

It's XP, there are likely several unpatched escaping bugs with free POC out there. You don't need anything new.

[–] [email protected] 20 points 6 months ago (1 children)

Surely breaking out of a VM requires exploiting a vulnerability of the VM, not of the OS running in it?

[–] [email protected] 4 points 6 months ago (2 children)

I would assume it requires both a hypervisor and guest OS bug to be tripped.

[–] [email protected] 4 points 6 months ago (1 children)

It's pure speculation, but I assume you'll need

  1. Enough access to the guest OS so that you can interact directly with the virtual hardware. That would probably require root access, so you'll probably need to exploit some bug in the guest OS to get there.
  2. To break out of the vm, you'll then need to exploit a bug in the virtual hardware. You would want to get the hypervisor to execute arbitrary code.
  3. If you want to infect the host OS, then you'll need sufficient access on the host. If the hypervisor doesn't run with sufficient privileges, you'll have to exploit a bug in the host as well to perform a privilege escalation. But I'm guessing the hypervisor will usually have sufficient privileges, so exploiting the host is probably not necessary.

Sounds like quite a bit of work, but I don't see why malware couldn't automate it. An up-to-date hypervisor should help reduce the risk though.

[–] [email protected] 5 points 6 months ago (1 children)

Theres no way an hypervisor zero day gets implemented in some random Malware. Those are worth millions and are used in coordinated manual attacks against VIP targets

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

Yeah a zero-day would be very unlikely, but a months-old, publically known and patched vulnerability could always be attempted. One of the reasons why the hypervisor should definitely be kept up-to-date. There is always someone who forgets to patch their software, why not give it a try? We're talking about a Windows XP scenario after all!

[–] [email protected] 1 points 6 months ago

It's XP. There's guaranteed to be a way to go from userland to ring 0 code execution.