Matan Berson (@MtnBer) header
Matan Berson (@MtnBer) profile picture

Hacker and bug bounty hunter mostly focusing on client-side security. h1-702 Vigilante, h1-65 Eliminator, AWC23 Best New Hacker

Joined May 2020
Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)Photo by Matan Berson (@MtnBer)
Just released my blog post "Bidding Like a Billionaire - Stealing NFTs With 4-Char CSTIs"! It's about a very impactful and technically interesting client-side bug I found in a major NFT site. matanber.com/blog/4-char-cst…
17
65
4
392
40,440
This is genius
I've released a DOMLogger++ config that helps detect any replacements occurring in a DOMPurify output by inserting and tracking a canary value at runtime. I think it highlights how useful DOMLogger++ can be for tracking JS execution :D 👉 github.com/kevin-mizu/domlog… 1/3
1
2
32
4,155
I’m in a pwnfunction video! Check it out, it’s very well made and the vulnerability chain is quite unique youtube.com/watch?v=RLyhPGsE…
3
22
2
172
13,861
I’m very excited to be part of the team! I can’t wait to collaborate with all of these amazing hackers and learn from them
The moments when I'm most proud of CTBB Podcast are the moments when we're discussing original, HQ research on the pod. So, that's why we're starting the Critical Research Lab with this tremendously talented group of researchers:
5
2
110
7,824
Here's a code snippet that as far as I can tell pretty much solves prototype pollution. It's based on github.com/tc39/proposal-sym…, and after running it you can access an object's prototype with object[Symbol.instanceProto], and object["__proto__"] will be undefined.
4
4
1
86
8,453
I love “constructor” and “__proto__”. Those two properties cause so many unexpected bugs
3
3
51
5,639
Ignoring backwards compatibility, I think prototype pollution can be pretty much solved by disabling access to __proto__ with bracket syntax ([]), and only allowing access to it with dot syntax
1
9
1,850
This was a good one, I’m proud of it. We managed to get very technical and even drop a new technique while not requiring too much prior knowledge Thanks to @ctbbpodcast for having me again
New episode focused on Browser Extension Hacking is live with @MtnBer! We cover the structure of browser extensions, the threat model for each component, and some practical vulnerabilities/common mistakes. Very practical episode. youtube.com/watch?v=ziP4cx_c…
1
1
54
2,950
Great trick by @kevin_mizu! I always thought caches were scoped to the current JS context, but apparently they’re scoped to the entire origin
I was really surprised to see that the Cache API is exposed on window, allowing a simple XSS to hijack a service worker and achieve persistent XSS on most pages of a vulnerable website! It might not be a new, but I feel like it is an incredible XSS leveraging gadget :D
2
20
2,645
I just want to have window.open. Is that too much to ask for?
3
23
3,480
I love the idea of people accidentally linking my h1 profile or something when trying to discuss JS stuff
1
11
1,100
Continuing the @PortSwiggerRes streak, @garethheyes just gave a completely mindblowing talk about email addresses! I was completely stunned by some of the things he mentioned there. He also gave me a copy of his amazing book JavaScript for Hackers 😄
5
110
5,446
Wow. @albinowax’s web timing attacks talk was absolutely incredible. I’m speechless
2
3
79
7,402
Just noticed the for the whole episode I did on the @ctbbpodcast I was talking through my camera’s mic and not through the good mic I bought specifically for that episode😭😭😭
7
54
5,557
I’m always surprised about how many devs overlooks this. I have found pretty much this exact issue in the chrome devtools frontend. If you don’t know the answer to this then 1. You should go and read “JavaScript for Hackers” by @garethheyes 2. Put a \r, \n or \t in the scheme
This Post is from an account that no longer exists. Learn more
1
8
65
8,787
I thought I knew pretty much all there is to know about CSPT and I couldn’t be happier to be proven wrong. I bet if you can pollute body params with query params in one endpoint you can probably do it everywhere, so because CSPT is usually systemic I bet you can wreck that target
CSPT is my favorite vuln type - and I yap about it on @ctbbpodcast all the time. I've been reporting CSPTs for the past 2 years+ now, so in light of the new research dropped by @Doyensec, let me drop a couple of takes on this🔥research:
2
27
4,200
Does anybody know a way to exploit document.head.innerHTML = location.href? Every payload I put in the query or the hash gets URL encoded
3
1
10
2,692
The preview for my latest blog post "Bidding Like a Billionaire - Stealing NFTs With 4-Char CSTIs" is out for the Critical Tinkers tier on the @ctbbpodcast discord👀 It's about a really sick bug so I can't wait to release it and share it with all of you
3
1
37
4,545
Mobile hunters - how do your bugs usually get rated in terms of CVSS? More specifically: What are AC and UI usually set to in an attack that requires a malicious app to be installed? Are there any common scenarios where Scope is usually set to changed (like reflected XSS in web)?
4
19
4,864
This might be one of the best resource investments I've made, the exclusive perks and content are so good
Another top hacker joins the CTers! Thanks for the sub @MtnBer ❤️
2
3
29
6,529
Also, from now on I'll start posting previews of my latest blog posts in the critical-thinkers channel a few days before I release them. There's a good one coming up on some advanced client side template injection exploitation so stay tuned!
17
1,762
These @hackerscrolls tips are so good
There is a popular opinion: bad CORS like <Access-Control-Allow-Origin: *> is unexploitable. Browser won't send cookies in this case. It is a delusion. You can exploit it with a Chrome cache feature! For example: hackerone.com/reports/761726 #BugBountyTip #CyberSecurity #BugBounty
2
3
36
4,549
‼️This technique is probably fixed nowadays. Thanks for noticing that @Rhynorater
3
1,555