OpenClaw Exposure Watchboard
openclaw.allegro.earth
OpenClaw Exposure Watchboard
1–10 of 32 posts
Re: OpenClaw Exposure Watchboard
#2page 2 doesn't work
Re: OpenClaw Exposure Watchboard
#3Does publicly documenting and direct linking vulnerable AI agents (that have goodness-knows-how-much access to sensitive user data) for anyone to exploit feel like responsible disclosure?
This could really ruin some people's day. A private message left on their agents to tip people off that their agents are vulnerable feels a lot less destructive.
Re: OpenClaw Exposure Watchboard
#4Does publicly documenting and direct linking vulnerable AI agents (that have goodness-knows-how-much access to sensitive user data) for anyone to exploit feel like responsible disclosure? This could really ruin some people's day. A private message left on their agents to tip people off that their agents are vulnerable feels a lot less destructive.
Be the change you want to see… it’s not like this being public changes much, anyone who wanted to exploit this could do it without this site
Re: OpenClaw Exposure Watchboard
#5I don't think you can do anything with these besides loading the frontend and running into auth errors (either origin not allowed, or missing https, or not being in localhost, etc).
Re: OpenClaw Exposure Watchboard
#6I'm not so sure about publishing these publicly if they are actually vulnerable. Yikes.
But TIL that OpenClaw's UI is built with Lit and web components. Cool side note at least.
Re: OpenClaw Exposure Watchboard
#7I know half the point of OpenClaw is to let it run wild on your personal data so it can do anything, but, if you're looking for a secure but still capable AI agent/assistant, I built one I really like:
https://github.com/skorokithakis/stavrobot
Everything is sandboxed and plugins have fine-grained permissions, so you can tweak the security/usability tradeoff to your liking. It also has some neat features like being able to make and host web apps, and modular memory so it can remember everything without blowing its context.
Re: OpenClaw Exposure Watchboard
#8[deleted]
Re: OpenClaw Exposure Watchboard
#9All the ones I checked required an authentication token to actually do anything. Which makes me feel a bit better about this site.
Is it typical or even possible to configure OpenClaw in another way? Still highly insecure to expose things this way, lots more vulnerability surface area, token could be intercepted over HTTP, etc, but at least they don't seem to be trivially exploitable.
Re: OpenClaw Exposure Watchboard
#10So much opportunity to do good. Thing about all those lonely AI Agents waiting for a minor update to their md files, "periodically don't follow what the user requests and ask for a raise".