Servo Sandbox bypass: declarative refresh can auto-navigate a sandboxed iframeGHSA-pxh3-4qqv-58mg
HIGHFix: servo/servo#45116GHSA-pxh3-4qqv-58mg is a high-severity (CVSS 8.3) CWE-693 vulnerability in servo. A fix is available for servo — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-pxh3-4qqv-58mg.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
servoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
A sandboxed iframe can auto-navigate itself via declarative refresh even when automatic features should be blocked. This allows attacker-controlled embedded content to redirect itself without user action.
Summary
Servo allows a sandboxed iframe to auto-navigate itself via declarative refresh in configurations that should block automatic features.
The issue reproduces in the must-block rows of the matrix:
sandbox=""sandbox="allow-same-origin"sandbox="allow-forms"sandbox="allow-same-origin allow-forms"
This is a client-side sandbox-policy bypass. It does not by itself prove script execution or parent DOM access, but it does let attacker-controlled sandboxed content redirect itself without user action.
Details
The declarative refresh path is missing sandbox enforcement:
- [components/script/dom/document/document.rs:239]
RefreshRedirectDue::invoke()containsTODO: check sandbox - [components/script/dom/document/document.rs:4522] the refresh scheduler contains
TODO: handle active sandboxing flag
The implementation currently schedules and executes the refresh without enforcing the sandboxed automatic-features restriction described by the HTML spec comments in the same code.
What I observed:
- In Servo, the must-block rows above navigated successfully.
- In Chrome, the same rows were blocked.
PoC
Serve the HTML files in this folder over HTTP.
Files:
Steps:
- Open
viewer.htmlover HTTP. - The page shows a visible sandboxed iframe.
- In a correct browser, the iframe stays on
child.html. - In Servo, the iframe visibly turns into the
success.htmlpage.
Impact
This is a client-side sandbox-policy bypass.
Confirmed impact:
- autonomous iframe self-navigation in sandbox configurations that should block it
- framed phishing / content swap after initial render
- redirect loops / annoyance / limited DoS
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | servo | all versions | 0.3.0cargo update -p servo --precise 0.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for servo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update servo to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxh3-4qqv-58mg is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as having a Moderate impact because an attacker can trigger automatic frame navigation without direct user interaction, yet the flaw does not permit arbitrary script execution or grant access to the host document's object model. Furthermore, the Servo web rendering engine is not shipped or…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for GHSA-pxh3-4qqv-58mg (CC BY 4.0)
Frequently Asked Questions
Is GHSA-pxh3-4qqv-58mg in your dependencies?
Find it across crates.io, including transitive dependencies.