foobar7 (@foobar0x7) profile picture

IT Security Consultant & Bug Hunter.

Joined March 2019
I haven't posted in a while because of how the platform developed. With Musk declaring support for the right-wing extremist party in my country, I'm officially saying goodbye. Supporting German Nazism is unacceptable and I don't want to be a part of that.
1
1
1
360
I hope to see y'all on other networks!
1
194
On a related note: It would be great if bug bounty platforms would reduce their dependency on twitter. I understand why they can't up and leave. But maybe add alternative social network options to users profiles. Maybe cross-post a bit more (there are even tools for that).
179
Read-only IDOR is now P3 on @Bugcrowd VRT. So if an unauthenticated attacker can access the PII of all customers of a company, that's P3. 🤔
5
7
2,488
Hackers, an important one. e.g.: we heard that CVSS "PR" is handled inconsistently (should be PR:None for self-sign-up). We're transparently listing a set of Detailed Platform Standards for consistency across programs. Need your help -- what to cover next? docs.hackerone.com/organizat…
10
27
7
105
52,677
Is there a chance your XSS payload will fire as blind XSS in some admin backend? Then don't (also) use alert(1). Might spoil a bxss for you or someone else as internal dupe when you pop an alert for the admin. #bugbountytips
1
1
734
Because the dev that triggers it will see the alert first & will open an internal ticket (at least they should). console.log(1) is a decent alternative when you're lazy (as we all are ;).
1
461
Personally, I never really paid attention to this. But I think it's a good policy & I will try to follow it more in the future.
403
RCE in Apache OpenMeetings due to SQL weak comparison, unexpected application state, and null-byte injection. Check out the technical details in our latest blog post: sonarsource.com/blog/a-twist… #appsec #security #vulnerability
24
66
10,230
Good news, CVSS 4.0 spec has this line regarding Privileges Required (PR) : Self-service provisioned accounts, that may be necessary to attack a cloud service, do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
15
35
8
228
65,949
It would be nice if bug bounty platforms would standardize the OOS section. Most of it is copy-paste anyways. Right now, it's like: - missing headers - CVE without working POC - boring - boring - oh yeah, XSS, IDOR, and RCE are OOS right now - boring - boring
1
3
17
3,940
If platforms categorized common stuff, it could look like this: Standard low/no impact cat 1: - missing headers - CVE without working POC Standard low/no impact cat 2: - [...] The programs custom OOS: - oh yeah, XSS, IDOR, and RCE are OOS right now
3
634
The Visma #1337up1122 Live Hacking Event has ended! 🏆 With 784 submissions and over €190,000 paid out, this was a major success, all thanks to @HackersMother @alicanact60 @putsi @JJaaskela @MattiBijnens @foobar0x7 @djurado9 @nytr0gen_ @hipotermia @p4fg @marcolivermunz @0x7yr
7
22
4
151
#1337up0822 was my first LHE in a while, and it has been so much fun here in Antwerp. I met awesome new people and had a great time hacking. Thanks @intigriti and @TheParanoids for having me and for hosting such an amazing event!
1
23
XSS payload to bypass CSP on innerHTML: <iframe srcdoc="<script src=//whitelisted.com></script>">
1
3
18
This is useful given an XSS vulnerability like x.innerHTML='[userinput]' & a CSP which can be bypassed (eg by uploading a JS file to a whitelisted domain or abusing a JSONP endpoint in it).
1
1
4
The naive approach of x.innerHTML='<script src=//whitelisted.com></script>' wouldn't work (script tags are not parsed in innerHTML in HTML5), but using an iframe can bypass this. The original DOM can be accessed via top.document.
1
5
In my experience, your evaluation has *a lot* of impact on the final bounty; programs highly value your expertise on severity assessment and many never touch severity themselves. So it's important to give the evaluation the proper attention.
1
1
4
If it's only an initial suggestion which shouldn't be taken too seriously, maybe the mechanism should be changed (display researcher & triager suggestion to the program side by side & let them build their own score)
1
3
Writing vulnerable code and playing with it is a great way to understand vulnerability classes.
Hackers, for the next 12 hours I’m going to run an experiment: you tell me which vulnerability class you want to learn more about and I will write vulnerable code so you can run and exploit it locally. Tweet me the vuln type and I’ll add code to a repository. #TogetherWeHitHarder
3