-
-
Notifications
You must be signed in to change notification settings - Fork 167
fix(security): deny window.open + block foreign navigation on all BrowserWindows (#377) #387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| import { test, expect } from '../fixtures/electron'; | ||
|
|
||
| /** | ||
| * T1 — renderer-only, mock IPC, no backend. Proves the #377 BrowserWindow | ||
| * hardening: the main window's `setWindowOpenHandler` denies every popup, so a | ||
| * renderer `window.open(...)` (or a `target="_blank"` link) can never spawn a | ||
| * chrome-less in-app Electron window. `about:blank` is used deliberately — it is | ||
| * not an http(s)/mailto URL, so the deny path runs without the interactive | ||
| * window's `shell.openExternal` fallback launching a real browser tab in CI. | ||
| * | ||
| * Scope: this asserts the popup-deny guard, which is the primary renderer- | ||
| * reachable risk surface. The companion `will-navigate` guard (defense-in-depth | ||
| * against full-page navigation away from the bundled renderer) is deliberately | ||
| * NOT asserted here: modern Chromium already blocks the only hermetic navigation | ||
| * vectors (`data:`/`about:blank`/missing `file:`), so a fail-before-provable test | ||
| * isn't achievable without a networked http target (side effects). That guard is | ||
| * verified by code review + reasoning, not a test that would pass regardless. | ||
| */ | ||
| test('window.open is denied — no popup BrowserWindow is created (#377)', async ({ | ||
| launchApp, | ||
| }) => { | ||
| const { app, page } = await launchApp({ mockIpc: true }); | ||
|
|
||
| const windowsBefore = app.windows().length; | ||
|
|
||
| // If the deny handler failed, a new window would appear and fire this event. | ||
| // We assert the *absence* of that event within a bounded window (event-race, | ||
| // not a fixed sleep in the assertion). | ||
| const popupAppeared = app | ||
| .waitForEvent('window', { timeout: 1500 }) | ||
| .then(() => true) | ||
| .catch(() => false); | ||
|
|
||
| await page.evaluate(() => { | ||
| window.open('about:blank', '_blank'); | ||
| }); | ||
|
|
||
| expect(await popupAppeared).toBe(false); | ||
| expect(app.windows().length).toBe(windowsBefore); | ||
| }); |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.