@TurvSec@theXSSrat@AikidoSecurity No, we explicitly mention that same-tenant is out of scope for some scenarios. Cross tenant has always been in scope.
@theXSSrat@AikidoSecurity Not having it in scope doesn’t mean we don't care about it perse! The focus of the BBP was on different vuln. classes, and e.g. internal efforts could get in the way of researchers, so having a vuln. class (temp.) out of scope actually helps to avoid that.
This reverse engineering work led its way to a fix in Chrome (subsequently Electron), with credit given back to me! Very cool to see, and happy to help the macOS ecosystem. I hope macOS fixes this huge issue soon. https://t.co/hfRxsF8uZM
when building ai products, the key is having some reliable signal about what is working and what is not. whether that signal comes from evals, user feedback, your own taste, performance metrics, or just gut feel does not really matter as long as it is giving you actionable information about where to focus your efforts.
the mistake is either having no signal at all (just building blindly) or getting caught up in the methodology of the signal rather than its utility. a formal eval that tells you nothing useful is worse than informal feedback that clearly points to real problems
@rez0__ Bug bounty hunting, on at least web applications, has always been about discovery instead of exploitation. Exploitation has always been straightforward in most cases (excluding escalating issues into more severe bug classes). So, the work here by @Xbow is definitely impressive.
A fix from Google was released today. Part of the issue was due to my misunderstanding based on previous reports.
Big thanks to chromium team for the quick resolve
I hope everyone had some fun, and apologies to the triagers on HackerOne XD
@Rhynorater Mostly because CSPT are not 1:1 reproducible across targets. It’s a novel approach every single time (esp. when chaining bugs), which makes it a beautiful bug class.
We did it! We tested 300 Bay Area foods for plastic chemicals. We found some interesting surprises.
Top 5 findings in our test results:
1. Our tests found plastic chemicals in 86% of all foods, with phthalates in 73% of the tested products and bisphenols in 22%. It's everywhere.
2. We detected phthalates in most baby foods and prenatal vitamins.
3. Hot foods which spend 45 minutes in takeout containers have 34% higher levels of plastic chemicals than the same dishes tested directly from the restaurant.
4. The 1950s Army rations we tested contained surprisingly high levels of plastic chemicals.
5. Almost every single one of the foods we tested are within both US FDA and EU EFSA regulations.
Check out our full results below.
in a couple weeks, i built a nuclear fusor in my bedroom – with zero hardware experience
the secret? Claude sonnet 3.5 + projects
a glimpse into the process below
Pass-the-{token} attacks are still very much relevant.
Tokens may change: Cookie, NT Hash, Kerberos ticket, MFA token, ...
However, the problem is not in the "token" but in the "pass".
We need a solutions to make tokens stay put, such as device and channel binding.
@charafmrah@benawad IMO it is fine. There is usually other ways to achieve persistence, e.g. by inviting your own user account to an affected tenant, changing the user's e-mail address, linking a social login account, creating an API key, etc.
The impact of a XSS doesn't really change.
My latest blog about my discovery for Evernote Client All-platform RCE via PDF.js font-injection to preload.js exposed ipcRenderer-BrokerBridge-boron.actions bypassing Electron's nodeIntegration | context-isolation;
Enjoy reading!
https://t.co/44uqjkChaI
I love crossover bugs that go between web/mobile/native because there's so much strange interactions that occur and a lot can go wrong - this research was another result of this!
https://t.co/m4XULDBXQ7