We at @pdiscoveryio are looking to hire a cracked security researcher.
priority on heavy CTF background & pure research experience over standard bug bounty work.
need high agency, total ownership, zero hand-holding. looking for the absolute best in the game. DMs are open
RTs/likes for reach appreciated!
Seems that wp2shell PoCs are now floating around the internet, so we've published our blog post including our research methodology for finding the bug as well as a deep dive into the chain itself - https://t.co/iuU0yiYJBT
Congrats! Skyvern is one of the cooler tools I’ve played around with in the past few months. Tons of opportunities with web automation and it works really well.
1/ We just raised $2.7M to give AI "hands" to do real work. 🚀
Browser automation has been broken for 20 years. If a button moves 10 pixels, your script breaks.
Meet Skyvern: The open-source agent that fixes the "maintenance tax" of automation.
@DanielMiessler Agreed here. I think a lot of bug bounty hunters/platforms conflate “vulnerabilities” vs “exploits”. The actualized risk of prompt injection comes from exploitability, otherwise it’s just a feature.
My thoughts on whether or not prompt injection is a vulnerability or a delivery mechanism.
Pros and cons for both sides of the debate...
https://t.co/XkdUnGOI0v
@InsiderPhD Exploiting a vulnerability and providing details is what people write blogs about and create CVE hype over.
Asking for responsible disclosure is a good start to preventing 0days from dropping. Adding requirements to the researchers hurts this.
@InsiderPhD I think it’s fine to argue it’s more “ethical” or “moral” to submit a patch, but I don’t think it’s something that should be an expectation or that researchers should inherently do when they find bugs.
@InsiderPhD Devs (should) know their codebase best. Offsec folks are best at digging into bug classes and patches to find new vectors. Both should play to their strengths.
Collaboration is obviously the best case. Sometimes pressure from disclosure is needed to get a response or action.
@InsiderPhD The vuln reporter should be providing recommendations to fix the issues (not necessarily a patch). The devs may implement those recommendations or apply an entirely different solution.
Sure for trivial patches, but a discussion is better initially for more complex bugs.
Made a writeup on a critical CVSS 10.0 vulnerability I've recently found. Check it out, maybe you'll manage to make into a full config independent RCE.
https://t.co/jQoTvtZ5Oe