This isn’t new at all. This is called session hijacking, and it’s been around for decades.
LTT just made a couple videos about it last year, because it happened to them.
this post was submitted on 08 Jan 2024
198 points (93.4% liked)
Technology
60052 readers
2816 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
I would guess they invalidate all sessions when password is reset, that part is weird.
Edit: read the thing. The exploit is that they steal some special token chrome stores and by manipulating it they can generate session cookies for the hijacked account. This doesn't seem related to ltt
Wow, this sounds a lot more serious than session hijacking. Are they straight up using Chrome's special token to generate brand new Google Account session tokens?
If so, i'm not sure how Google is going to fix that without wrecking the Chrome user experience for non tech savvy individuals
~~They're using some Google api to generate the cookie(s?) with the manipulated chrome token. To me it kinda sounded like Google is using an improper method to generate the chrome token and the hackers found a way to derive other valid chrome tokens from it.~~ Though I'm not an expert. Read it yourself to get the right picture.
Edit: This is the part of the article about it, rest seems to be about how the hackers encrypted their exploit to avoid detection:
Lumma's approach hinges on a nuanced manipulation of the token:GAIA ID pair, a critical component in Google's authentication process. This pair, when used in conjunction with the MultiLogin endpoint, enables the regeneration of Google service cookies.
By manipulating the token:GAIA ID pair, Lumma can continuously regenerate cookies for Google services. Even more alarming is the fact that this exploit remains effective even after users have reset their passwords.
Edit but there's some conflicting information on what to do:
If you suspect your account may have been compromised, or as a general precaution, sign out of all browser profiles to invalidate the current session tokens. Following this, reset your password and sign back in to generate new tokens. This is especially crucial for users whose tokens and GAIA IDs might have been exfiltrated. Resetting your password effectively disrupts unauthorized access by invalidating the old tokens which the infostealers rely on, thus providing a crucial barrier to the continuation of their exploit.
From one of the hack tool changelogs:
Now "Google Accounts" folders will appear in the logs , containing txt with tokens that can be used to restore Google cookies ; also, cookies restored in this way do not die after changing the password
I guess Google doesn't invalidate session cookies generated with the chrome token upon a password reset, but the chrome token itself gets invalidated and deletes the session cokkies on the browser side or something? Idk sounds whack
I thought session hijacking could only be done with 1st party cookies from google itself. I didn't know you could session hijack with 3rd party cookies. That's pretty interesting.
The article mentions third party cookies, but it’s talking about hackers stealing first party cookies (specifically authentication cookies).
Firefox users keep winning.
Firefox isn't magically immune to session hijacking...
This isn't session hijacking but taking some magical token from Chrome that can generate sessions. Which has far more attack surface.
So it is session hijacking, something that has been known for a while?
The main difference that makes this worse is that they can get persistence and maintain access even if the user resets their password (i.e. revoke session tokens). Hackers are usually limited to the fairly short lifetime of the session token (usually a few hours).
Yes, if by for a while you mean 25 years or so.
So the moral is use Firefox and not Chrome?!
This is the best summary I could come up with:
Analysis from security firm CloudSEK found that a dangerous form of malware uses third-party cookies to gain unauthorised access to people’s private data, and is already being actively tested by hacking groups.
The post noted how accounts could be compromised through a vulnerability with cookies, which are used by websites and browsers to track users and increase their efficiency and usability.
The Google Chrome web browser, which is the world’s most popular with a market share greater than 60 per cent last year, is currently in the process of cracking down on third-party cookies.
“This exploit enables continuous access to Google services, even after a user’s password is reset,” Pavan Karthick M, a threat intelligence researcher at CloudSEK, wrote in a blog post detailing the issue.
“It highlights the necessity for continuous monitoring of both technical vulnerabilities and human intelligence sources to stay ahead of emerging cyber threats.”
The security issue was detailed in a report, titled ‘Compromising Google accounts: Malwares Exploiting Undocumented OAuth2 Functionality for session hijacking’, written by CloudSEK threat intelligence researcher Pavan Karthick M.
The original article contains 335 words, the summary contains 177 words. Saved 47%. I'm a bot and I'm open source!