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.
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
foobar7 retweeted
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…
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
foobar7 retweeted
Check out more questions like this here 👇
github.com/hakluke/bug-bount…
foobar7 retweeted
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
foobar7 retweeted
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.
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
foobar7 retweeted
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
#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
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).
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.
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










