slonser Profile
slonser

@slonser_

Followers
2K
Following
161
Statuses
84

@C4TBuTS4D CTF team. Security Researcher at Solidlab. Web3 research at @neploxaudit

Joined December 2023
Don't wanna be here? Send us removal request.
@slonser_
slonser
27 days
In 2024, I interacted a lot with Extensions. I decided to create a resource that will help with a basic understanding of extensions and key attacks. P.S. I tried to make everything as clear as possible and hope it won’t feel too overwhelming anywhere.
11
94
315
@slonser_
slonser
17 hours
Therefore, you can simply insert > and load your resource. This is useful in cases where the header is set only for successful search queries, as it allows performing an XS-Leak attack.
Tweet media one
0
0
5
@slonser_
slonser
3 days
@WeizmanGal Some of the examples that will be shown and the anti-patterns of development are applicable to Metamask; however, Metamask is quite secure and one of the few wallets where a complete exploitation chain could not be achieved. ;)
1
1
11
@slonser_
slonser
3 days
As always, top-notch! You must read this!
@kevin_mizu
Kévin GERVOT (Mizu)
3 days
I'm very happy to finally share the second part of my DOMPurify security research 🔥 This article mostly focuses on DOMPurify misconfigurations, especially hooks, that downgrade the sanitizer's protection (even in the latest version)! Link 👇 1/2
0
0
12
@slonser_
slonser
8 days
Small writeup on my 0day at Casdoor (not fixed yet) Abusing open redirect via pwa protocol handlers
2
27
102
@slonser_
slonser
8 days
@xvonfers Sounds interesting 😸
0
0
0
@slonser_
slonser
9 days
Great talks! I'm happy that @kevin_mizu research made it into the top 10—he deserves it. A bit sad that I didn’t make it into the top 10, though. It seems that research related to Chrome isn’t very interesting to the community, so maybe I should try something different in 2025.
@PortSwiggerRes
PortSwigger Research
9 days
The results are in! We're proud to announce the Top ten web hacking techniques of 2024!
4
1
50
@slonser_
slonser
22 days
RT @d4d89704243: Introducing the Cookie Sandwich, a tasty technique to steal HttpOnly cookies using legacy RFC features:
0
85
0
@slonser_
slonser
23 days
@hackermondev So cool research! Thanks for sharing
0
0
0
@slonser_
slonser
25 days
@kinugawamasato Yeah, I know, I accidentally sent an unfinished example to the server while uploading another update :) I'm working on adapting a real example to make it less bulky and to avoid getting penalized for disclosure. Sorry about that.
0
0
2
@slonser_
slonser
26 days
@RenwaX23 Hmmm, In my cases, it didn’t cause any issues, but thank you! I’ve added a note about it to the article.
1
0
1
@slonser_
slonser
26 days
@kinugawamasato Hi! Yes, in this case, it really isn't necessary. My mistake— I tried to oversimplify the example to make it easier to understand XD I am going to update the article with a different example, thanks for your help!
1
0
4
@slonser_
slonser
26 days
@TheGrandPew Yes, I didn’t phrase it quite correctly. Initially, I meant it in the context of rewriting the document object. I will revise the article and elaborate on this point in more detail. Thank you for your help!
Tweet media one
0
0
2
@slonser_
slonser
27 days
RT @neploxaudit: Can you find an error in the following Chrome extension content scripts? If not, you might want to check out our knowledge…
0
3
0
@slonser_
slonser
27 days
Also Added mini Writeup to my Chrome CVE-2024-10229 here -
1
4
23
@slonser_
slonser
29 days
@albinowax @kobi_hk Therefore, if you have access to modify headers (and can insert an arbitrary content-type), it's game over. You simply gain control over the Service Worker.
1
0
3
@slonser_
slonser
29 days
@kevin_mizu But there's a chance that the first part will make it into the top of 2024, and the second one into the top of 2025 XD
1
0
1