Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Security: outsourc-e/clawsuite

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability in ClawSuite, please report it responsibly.

Do NOT open a public GitHub issue for security vulnerabilities.

Instead, email: security@clawsuite.io

We will acknowledge your report within 48 hours and aim to provide a fix within 7 days for critical issues.

Scope

  • ClawSuite web application code
  • API routes and gateway communication
  • Authentication and session management
  • Client-side data handling and rendering
  • Exec approval and human-in-the-loop controls
  • Browser proxy and screenshot endpoints

Out of Scope

  • OpenClaw gateway itself (report to OpenClaw)
  • Third-party dependencies (report to the respective maintainer)
  • Social engineering attacks

Security Measures (v3.0.0+)

Authentication

  • All API routes require authentication as of v3.0.0
  • Session tokens use timing-safe comparison to prevent timing attacks
  • httpOnly + SameSite=Strict cookies
  • Token revocation on logout

Network

  • Access-Control-Allow-Origin restricted to localhost — no wildcard CORS
  • Browser proxy and screenshot endpoints locked to same-origin only
  • Rate limiting on high-risk endpoints (file access, debug, exec)

Data & File Access

  • Path traversal prevention on all file and memory routes (ensureWorkspacePath())
  • .md-only restriction on memory write routes
  • No API keys or secrets ever exposed to client-side code
  • Gateway tokens are server-side only
  • Diagnostic output scrubbed of sensitive data

Agent Safety

  • Exec approval workflow — sensitive gateway exec commands require explicit human approval via in-UI modal
  • Skills security scanning — every skill from the marketplace is scanned for suspicious patterns before install

Configuration

  • Environment files are gitignored
  • Config endpoints redact credentials in responses
  • Example configs use placeholder keys only

Security Audit Passes

SEC-3 (2026年02月25日)

  • Completed full API audit for auth coverage; no new private route auth gaps found (/api/config-get, /api/debug-analyze, /api/context-usage, /api/paths verified authenticated).
  • Added CSRF content-type enforcement (requireJsonContentType) to remaining POST handlers, including auth and terminal management endpoints.
  • Tightened rate limiting to 10 requests/minute per IP (sliding window) on high-risk endpoints:
    • /api/terminal-input
    • /api/terminal-stream
    • /api/gateway-restart
    • /api/update-check (POST)
    • /api/openclaw-update (POST)

Supported Versions

Version Supported
v3.x (main) ✅ Active
v2.x ⚠️ Security fixes only
< v2.0 ❌ Unsupported

There aren't any published security advisories

AltStyle によって変換されたページ (->オリジナル) /