D3D11: Fix respecifying 3D textures
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
People
(Reporter: jrmuizel, Assigned: jgilbert)
References
Details
(Keywords: csectype-bounds, sec-high, Whiteboard: [sec-survey][adv-main90+][adv-esr78.12+])
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
tjr
:
approval-mozilla-beta+
tjr
:
approval-mozilla-esr78+
tjr
:
sec-approval+
|
Details | Review |
167 bytes,
text/plain
|
Details |
We found out about https://chromium-review.googlesource.com/c/angle/angle/+/2911032.
The details are unclear. Jeff Gilbert is going to investigate.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Yeah, seems clear we need this. Here's our code, clearly unpatched:
https://searchfox.org/mozilla-central/rev/af8e5d37fd56be90ccddae2203e7b875d3f3ae87/gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Image11.cpp#226
We're unlikely to be covered elsewhere. I'm requesting access to the Chromium issue, so I'll be able to know more, but this seems pretty cut-and-dry.
I'll get this cherry-picked for us.
Comment 2•3 years ago
|
||
Jeff, FYI, I am planning to do an 89 dot release (not security related) next week, building it on Monday and probably shipping on Wednesday, should I wait for this patch to be included in this dot release or is it a fix that can ride the 91 train? Also, do you know if ESR and mobile are affected? Thanks
Assignee | ||
Comment 3•3 years ago
|
||
I'll have patches up today. Expect all branches to be effected.
This is simple enough that it could be a ride-along, and Chrome thought it was serious/high severity. (OOB write)
Assignee | ||
Comment 4•3 years ago
|
||
- Handle blank lines in moz.yaml.
Assignee | ||
Comment 5•3 years ago
|
||
Comment on attachment 9226631 [details]
Bug 1715766 - [angle] Cherry-pick 3d texture respec fix.
Security Approval Request
- How easily could an exploit be constructed based on the patch?: Medium-hard. The upstream commit fix is vague, but it given the sec bug marking here and upstream, it's clear there's more to this. The upstream commit (that we cherry-pick) does include a test, but turning that into a useful exploit is fairly hard.
- Do comments in the patch, the check-in comment, or tests included in the patch paint a bulls-eye on the security problem?: Yes
- Which older supported branches are affected by this flaw?: all
- If not all supported branches, which bug introduced the flaw?: None
- Do you have backports for the affected branches?: No
- If not, how different, hard to create, and risky will they be?: It should backport cleanly
- How likely is this patch to cause regressions; how much testing does it need?: Unlikely to cause regressions: Small fix, taken (and uplifted) upstream.
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Comment on attachment 9226631 [details]
Bug 1715766 - [angle] Cherry-pick 3d texture respec fix.
Approved to land and uplift
Updated•3 years ago
|
Comment 7•3 years ago
|
||
[angle] Cherry-pick 3d texture respec fix. r=lsalzman,jrmuizel
https://hg.mozilla.org/integration/autoland/rev/743226a3d588
https://hg.mozilla.org/mozilla-central/rev/743226a3d588
Comment 8•3 years ago
|
||
uplift |
Comment 9•3 years ago
|
||
uplift |
Comment 10•3 years ago
|
||
As part of a security bug pattern analysis, we are requesting your help with a high level analysis of this bug. It is our hope to develop static analysis (or potentially runtime/dynamic analysis) in the future to identify classes of bugs.
Please visit this google form to reply.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 11•3 years ago
|
||
Updated•3 years ago
|
Comment 12•3 years ago
|
||
Updated•3 years ago
|
Description
•