I’m surprised people are still using OpenClaw. I assumed they’d have switched to Nanoclaw or Nemoclaw. Is OpenClaw just that much better, or is it all inertia?
(I’ve never used any of them.)
OpenClaw privilege escalation vulnerability
211–220 of 306 posts
Re: OpenClaw privilege escalation vulnerability
#212Re: OpenClaw privilege escalation vulnerability
#213> We're working hard to harden the codebase with folks from Nvidia, ByteDance, Tencent and OpenAI. But coding is solved? Why do you need those guys if all they do is use claude code? Just have it solve it overnight. You forgot to prompt "make it secure pls"?
Coding is solved, but problems with code is not yet solved.
Re: OpenClaw privilege escalation vulnerability
#214OpenClaw creator here. This was a privilege-escalation bug, but not "any random Telegram/Discord message can instantly own every OpenClaw instance." The root issue was an incomplete fix. The earlier advisory hardened the gateway RPC path for device approvals by passing the caller's scopes into the core approval check. But the `/pair approve` plugin command path still called the same approval function without `callerS…
[flagged]
Re: OpenClaw privilege escalation vulnerability
#215Earlier quoted context omitted.
> We're working hard to harden the codebase with folks from Nvidia, ByteDance, Tencent and OpenAI. What exactly does this mean? You have contracts with these companies? People who work for them contributed sometimes in the past to openclaw repository?
If I am not mistaken steipete works for OpenAI now as part of OpenClaw being acquired by them back in February. NVIDIA is contributing to the security of OpenClaw via NemoClaw.[0] Not sure about ByteDance and Tencent. 0. https://www.nvidia.com/en-us/ai/nemoclaw/
[flagged]
Re: OpenClaw privilege escalation vulnerability
#216I’m surprised people are still using OpenClaw. I assumed they’d have switched to Nanoclaw or Nemoclaw. Is OpenClaw just that much better, or is it all inertia? (I’ve never used any of them.)
I'm using Hermes. The same applies to all agents, don't give it free reign over all your stuff. Run it within a sandbox.
Re: OpenClaw privilege escalation vulnerability
#217OpenClaw creator here. This was a privilege-escalation bug, but not "any random Telegram/Discord message can instantly own every OpenClaw instance." The root issue was an incomplete fix. The earlier advisory hardened the gateway RPC path for device approvals by passing the caller's scopes into the core approval check. But the `/pair approve` plugin command path still called the same approval function without `callerS…
I could not stop myself from looking at this user's submission history, looking for a ShowHN about Clawdbot. No such submission exists. I can understand why, but given that OpenClaw has taken over the world, I find the lack of a ShowHN somewhat interesting.
The hype was entirely manufactured from day 1.
Re: OpenClaw privilege escalation vulnerability
#218I’m surprised people are still using OpenClaw. I assumed they’d have switched to Nanoclaw or Nemoclaw. Is OpenClaw just that much better, or is it all inertia? (I’ve never used any of them.)
[dead]
Re: OpenClaw privilege escalation vulnerability
#219Earlier quoted context omitted.
What is OpenClaw doing here that Claude Desktop or Claude Code couldn't do?
Claude Desktop and Code are built for synchronous, human-in-the-loop interactions. Scraping 3000 janky municipal websites, you need a "fire-and-forget" background worker. Claw lets you kick off a massive job and just get a ping when it's done. I'd also instantly hit Claude Desktop's rate limits with this I reckon. Since Claw uses APIs, you bypass those limits and can route the messy scraping to cheap models, saving e…
I would first automate everything with scripts, and only use an agent for the parts that require it.
For example you mentioned playwright? That can be automated. It doesn’t need to be a free form tool that the agent uses at will.
If that means the scripts need to be adopted to changes, then that’s a separate, controlled workflow.
This approach can save you a ton of tokens, increasee reliability and observability, and it saves compute as well.
Sometimes it‘s useful to let the agent do things fully agentic, so you can then iteratively extract the deterministic parts.
Re: OpenClaw privilege escalation vulnerability
#220Earlier quoted context omitted.
Why?
It breaks several guidelines: Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes. Comments should get more thoughtful and substantive, not less, as a topic gets more divisive. Please don't fulminate. Please don't sneer. Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. The guidelines still apply, even if you feel nega…
Thanks for explaining, is this mostly about replying directly to the person involved in the project? Compared to e.g. a comment in a thread about OpenClaw without replying directly to the creator? Just trying to figure out where the line is, I do think snark is a valid form of criticism sometimes but it's your house after all.