this post was submitted on 21 Mar 2024
23 points (96.0% liked)

PC Gaming

8573 readers
299 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] c10l@lemmy.world 1 points 7 months ago (1 children)

Has this been established? Have EA published their findings somewhere?

[–] ILikeBoobies@lemmy.ca 1 points 7 months ago (1 children)

Not yet, EAC and EOS have stated their investigations have not found the vulnerability on their end. Respawn has yet to comment on it at all

[–] c10l@lemmy.world 1 points 7 months ago

Ok so it’s unknown.

Whilst I agree that it’s unlikely that it was an RCE in EAC like it’s been floating around, nothing can be entirely discarded yet.

I do agree that it’s likely safe to play Halo, if the hack happened due to calls made from Apex to EAC, that means EAC’s APIs made it possible (still unlikely to be an RCE though). With that in mind, bugs or malicious code in any game that interacts with the EAC APIs could cause the same issue.

This is one of the dangers of kernel-level anti-cheat systems.

It should be safe(r) on Linux though, as it has no direct access to the kernel.