GHSA-x562-297c-g43g

Electron: Pointer lock permission requests can be attributed to the wrong frame

En bref

Publiée
Mise à jour
CVE
CVE-2026-113798
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Description

### Impact For `pointerLock` permission requests made from some cross-origin iframes, `session.setPermissionRequestHandler()` was given the top-level frame's `requestingUrl` and `isMainFrame` instead of the requesting frame's. Apps that grant pointer lock based on the requesting origin could grant it to embedded content under the top-level page's identity. Apps are only affected if they embed untrusted content in iframes and decide `pointerLock` requests by origin in `setPermissionRequestHandler`. Apps that do not embed untrusted content, or that deny `pointerLock` for it, are not affected. ### Workarounds Deny the `pointerLock` permission for web contents that embed untrusted frames. ### Fixed Versions * `45.0.0-alpha.13` * `44.5.0` * `43.7.6` * `42.11.9` ### For more information If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org)

Paquets affectés

PaquetVersions
npm · electronintroduced 45.0.0-alpha.1, fixed 45.0.0-alpha.13
npm · electronintroduced 44.0.0-alpha.1, fixed 44.5.0
npm · electronintroduced 43.0.0-alpha.1, fixed 43.7.6
npm · electronintroduced 0, fixed 42.11.9

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database