In collaboration with a couple of other leaders in the industry we are releasing https://t.co/Kssdre4HiX - It's an attempt to provide transparency about role levels, expectations and (just for the US market currently, salary ranges). For leaders writing JDs and candidates alike.
Stop asking LLMs to “find vulns.” Start using them to understand code.
@Sw4mp_f0x walks through using Claude Code as a force multiplier in app assessments - faster analysis, fewer false positives, better outcomes.
Check it out: https://t.co/BpMnOGBMv7
@leune Very solid list 😁. Love to see Mr. Robot make the cut. Was really fun working while the show was coming out and having non security IT folk approach me about the scenarios/accuracy.
⚠️ Giveaway time! ⚠️ 👇
📢 Our new course "Attacking AI" will be Feb 27-28!
This two-day course equips security professionals with the tools and methodologies to identify vulnerabilities in AI systems. It's gonna be a BANGER.
Syllabus: https://t.co/cY9vcI7Z5y
We are giving away two seats this week!
⁉️How to enter the giveaway:
♻️ Repost this post = 2 Entries
🗣️ Reply = 1 Entry
❤️ Like = 1 Entry
Nothing helps me understand the "it works" mentality of a full-time dev better than going down a rabbit hole of docs and blogs for what I thought was the simple question "what's the 'best' way to get an IP address from a hostname in Python" 😂
@G0LDEN_infosec Yeah I've found it to be similar to "dreading" the gym. The thought of the session can be a daunting, but once you start you just hit the flow.
Witnessing a Total solar eclipse on an extremely cloudy day that magically got out of the way for totality really was one of the most surreal experiences of my life. Hope everyone got a chance to see!
The next cohort of "The Bug Hunter's Methodology Live" will be:
US: March 2nd-3rd
EU: March 9th-10th
https://t.co/VnOqGJ5Yyo
Repost, like, and reply for a chance at a free seat!
New in v2.5 - More Burp, more JS analysis, more IDOR/MFLAC!
Shoutout to @Jhaddix and his TBHM Live course for getting me to embrace mindmapping. All of the course content been game changing for my workflow and I couldn't recommend it more!
Checkout https://t.co/vPdA6f3kIk for when the next set of courses are being held!
@Jhaddix I was also not a fan of the mesh construction of HM. I ended up going with a steelcase Leap and it has lasted me 4 years of punishment (got it at start of COVID) and holding up real well!
Oof that was a tricky one but a good one
I completed the Web Security Academy lab:
Exploiting server-side parameter pollution in a REST URL
@WebSecAcademy
https://t.co/IrLFYOTfqX
Congratulations to @NahamSec for hitting the million-dollar milestone on HackerOne! 🤑 NahamSec’s passion for ethical hacking helps protect the world’s top organizations by finding potential vulnerabilities before cybercriminals. Amazing work! 👏
🕵️♂️ Show & Tell: Here's how I exploited a simple Issue on target app using GraphQL that allowed me to take over any user's account 💰💰
This is a classic case of thinking outside the "box." The app I targeted allowed Inviting users to your organization. When an invite is sent to the victim, they get a link like http://targetapp/invitation/{token}.
What was interesting was that the invitation link automatically logged a victim into their account and asked them if they wanted to accept the invitation.
🚨 This grabbed my attention, prompting the question, "Can I somehow acquire that Invitation token?" Considering its potential to let me take over any person's account, I immediately delved deeper into the app and came across a GraphQL operation for retrieving the list of invited users:
code[{"operationName":"GetPendingMembers","variables":{"ID":"XXXX"},"query":"query GetPendingMembers($ID: ID!) {\n users: GetPendingMembers(ID: $ID) {\n invited { email\n role\n createdAt\n updatedAt\n __typename\n }\n __typename\n }\n}\n"}]
Looking at this, I thought, "What if the 'invited' object has more info than shown?" So, I added the \n token parameter Inside the invited object:
code[{"operationName":"GetPendingMembers","variables":{"ID":"XXXX"},"query":"query GetPendingMembers($ID: ID!) {\n users: GetPendingMembers(ID: $ID) {\n invited {\n token email\n role\n createdAt\n updatedAt\n __typename\n }\n __typename\n }\n}\n"}]
Surprisingly, it worked! The GraphQL operation returned the token that was sent to victims email.
Crafted a URI with the leaked token, like http://targetapp/invitation/{token}, and took over the victim's account.
Lesson: Always think outside the box. Instead of just hunting for vulnerabilities, notice odd app behaviors— they might lead you to unexpected weaknesses. Understand how the app works, find flaws, and outsmart the design. 👾 #BugBounty #AppSecurity #ThinkOutsideTheBox #HackerOne #BugBountyTips #SecurityTips #BugCrowd #InfoSec #Bounties #Bounty #Tips #Follow