CTO @TrustedSec | Former Optiv/SecureWorks/Accuvant Labs/Redspin | Race cars
/tmp/.a
Joined April 2008
- Tweets67.7K
- Following5K
- Followers75.3K
- Likes146K
Yea I had an agent do this for hours earlier.
People are likely to run into other fun issues in the wild as well.
Hey
"The previous update (October 22 16:18 UTC) reported that Sophos observed successful exploitation of PHP2Shell in customer environments. Upon further analysis, we are correcting that assessment as Sophos customer telemetry shows scanning and a small number of failed exploitation attempts. As of this update, there is no evidence of a successful compromise due to these vulnerabilities." sophos.com/en-us/blog/proof-…
I hope people don’t forget how far off the majority of PoCs were from working in the real world 12-24 hours after news dropped.
One of the variants that works however per build offsets is annoying
Heap leak → recover heap and libphp base addresses → use known per-build offsets to resolve zval_ptr_dtor and zif_system, bypassing ASLR → place a forged HashTable at a predictable heap-relative address → trigger cleanup of the stale session reference → PHP follows the legitimate destructor path, invoking the forged pDestructor pointer → execution reaches zif_system, resulting in command execution.
Nobody ever wants to discuss fun things like abuse of functionality and the related topic backwards compatibility.
There is an info leak but you’re still dealing with offsetting from there for each php version and then whatever else people did to php.ini re memory size etc
We’re going to look back at this era when LLMs have supposedly solved software security, only for people to realize how much money is still being lost every year to BEC and other attacks that require little technical sophistication.
All while LLMs have arguably become the best BEC tooling on the planet.
Justin Elze retweeted
Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way. 🎉
We've heard from so many of our customers who want to use these new personal AI agents to help them get more done, but want more control over what the agent can access with the same trust and ease of use they get when using 1Password directly.
1Password for Agents gives your agents access without giving up your passwords. When an agent reaches a sign-in form, it requests a credential from your vault. If you approve the request, 1Password directly auto-fills the credential in the destination site so the agent can’t see or take possession of the credentials.
The agent gets the task done, but it doesn’t get your passwords..
You stay in control. 1Password for Agents free and optional for personal and family accounts. Unless you opt-in to an agent connector, agents cannot touch your vault.
➡️Learn more: bit.ly/487da6J
The hype leading up to this model, combined with all the “please stop us” rhetoric, is exactly how we got here.
