Skip to content
This repository was archived by the owner on Oct 31, 2026. It is now read-only.

Security: dario-cositore/OpenConnect

Security

SECURITY.md

Security Policy

Reporting Security Vulnerabilities

Do not open public issues for security vulnerabilities.

If you discover a security issue in OpenConnect, please report it privately:

Include:

  1. Description of the vulnerability
  2. Steps to reproduce
  3. Potential impact assessment
  4. Suggested fix (if any)

You will receive a response within 48 hours. We aim to resolve critical vulnerabilities within 7 days.

Security Hardening (Built-in)

OpenConnect includes the following security measures:

  • httpOnly cookies — JWT tokens are XSS-resistant (never in localStorage)
  • CORS lockdown — Restricted to known origins (app + hub domains)
  • CSP headers — Strict Content Security Policy
  • Selector sanitization — Blocks javascript:, data:, <script in selectors
  • Rate limiting — Registration and login rate limiting per IP
  • Anti-gaming — Daily caps, 24h account age, email verification requirements
  • Input validation — Pydantic models, max lengths, URL scheme validation
  • Docker hardening — Non-root user, NoNewPrivileges, ProtectSystem=strict

Known Limitations

  • Selectors defined in connector JSON are executed in a headless Chromium context. Maliciously crafted selectors cannot escape the Playwright sandbox.
  • The execution engine creates a fresh BrowserContext per execution — no shared state between user sessions.

Dependency Security

Direct dependencies are pinned in server/requirements.txt. We recommend running pip audit in your deployment pipeline:

pip install pip-audit
pip audit -r server/requirements.txt

There aren't any published security advisories