We don't add user font sandbox rules for the profile picker gpu process
Categories
(Core :: Security: Process Sandboxing, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox145 | --- | unaffected |
| firefox146 | --- | disabled |
| firefox147 | --- | fixed |
People
(Reporter: bobowen, Assigned: bobowen)
References
Details
Crash Data
Attachments
(1 file)
Analysis of the get_first_matching_font crashes from bug 1967071 revealed that they all had a GraphicsCriticalError containing "Shader disk cache is not supported".
We add rules to give access to this normally, but not in the profile picker, because GeckoDependentInitialize (where we cache the profile dir) is not called.
Currently, we also use the gecko directory service to cache the user's AppData\Local dir, so we don't add user font rules for the picker process either.
Looking at some of the dumps for these crashes, they all have various Segoe UI font file paths from the windows user's font dir in their stacks.
(Some with slightly odd names: i.e. with _0 or _1 appended as if they've been copied.)
This is odd because these should be in the system font dir as protected fonts.
It's not easy to override that, because only TrustedInstaller has full access to that dir and these are protected system fonts and a standard attempt to uninstall using the system font dialog gets blocked. I'm sure it is possible though.
We can easily get the AppData\Local dir from windows directly like we do for other dirs, so we can always add these rules.
| Assignee | ||
Comment 1•6 months ago
|
||
This means we can add user font rules for the profile picker gpu process.
| Assignee | ||
Comment 2•6 months ago
|
||
Comment 5•6 months ago
|
||
The patch landed in nightly and beta is affected.
:bobowen, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox146towontfix.
For more information, please visit BugBot documentation.
Updated•6 months ago
|
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Description
•