Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Scan browser runs without Chromium's sandbox

Aberta
  • Algo errado?
#331 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@eparenti já está trabalhando nisso.

Desde 29/10/2026.

  • #342 de @eparenti — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
46/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
playwright, typescript
Domínio
security, testing

Direção de pesquisa

Start in src/deps/real.ts at makeSharedBrowser and trace how launch failures, run output, doctor findings, and Result coverage are represented. Read the existing config and threat model, then locate the relevant tests and add coverage for default sandbox launch, all three fallback disclosures, and require refusing with exit 4. Done when those behaviors and the three specified CDP and browser threat model points are covered.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area: engine security

What happens

usabl launches its scan browser with chromium.launch({ headless: true }) (src/deps/real.ts, makeSharedBrowser). Playwright adds --no-sandbox unless chromiumSandbox: true is passed, and usabl never passes it. Every page usabl scans runs without Chromium's sandbox: the app, its docs pages, and any third-party scripts they load.

Why it matters

The sandbox is what contains a page that exploits a Chromium rendering bug. Without it, such a page runs code with the rights of the user running usabl. That user can read the repository, local keys, and the signed-in session from USABL_STORAGE_STATE. In CI, it can read the runner's tokens.

Decision

  • Launch with the sandbox on by default.
  • When the system cannot provide a sandbox (for example Ubuntu 23.10 and later with restricted user namespaces, or many containers), fall back to an unsandboxed launch and disclose it: a line in the run output, a usabl doctor finding with the fix, and a note in the Result's coverage section. The fallback changes no verdict.
  • A config option (for example "browserSandbox": "require") refuses to scan unsandboxed: exit 4 with a message that says how to enable the sandbox.
  • Tell a sandbox failure apart from other launch failures, so a missing Chromium or a crash is not reported as a sandbox problem.

Acceptance

  • A test proves the default launch asks for the sandbox.
  • A test proves the fallback is disclosed in all three places.
  • A test proves require refuses with exit 4.
  • The threat model gains a section on CDP and the browser covering three points. First, CDP runs over a pipe and no port is opened. Second, page-world reads versus isolated worlds. Third, the sandbox, plus a note that a caller's own browser passed to checkPage is the caller's exposure.

Notes

Checked on 2026-10-27. A scan browser carries --remote-debugging-pipe and --no-sandbox, and ss shows no listening TCP socket owned by it. A sandboxed launch works on a Fedora 43 host.

Linguagem predominante
TypeScript
Estrelas
0
Forks
0
Merge médio
6h 42min
PRs com merge (30d)
44

Preparar o ambiente

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de usabl-dev/usabl

Todas as issues de usabl-dev/usabl

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.