Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Scan browser runs without Chromium's sandbox

Offen
  • Stimmt etwas nicht?
#331 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@eparenti arbeitet bereits daran.

Seit 29.10.2026.

  • #342 von @eparenti — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
46/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
playwright, typescript
Bereich
security, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
0
Forks
0
Ø Merge
6 Std. 25 Min.
Gemergte PRs (30 T.)
46

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus usabl-dev/usabl

Alle Issues in usabl-dev/usabl

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.