Update crossbeam-channel.
Categories
(Core :: General, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox81 | --- | wontfix |
firefox82 | --- | fixed |
firefox83 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
(Keywords: sec-high, Whiteboard: [sec-survey][adv-main82+][post-critsmash-triage])
Attachments
(2 files, 1 obsolete file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
tjr
:
sec-approval+
|
Details | Review |
720 bytes,
text/plain
|
Details |
I don't know if this can be causing issues for our users, see incoming patch.
Assignee | ||
Comment 1•4 years ago
|
||
It's used by both webrender and fog, and it contains a subtle soundness
issue which may affect us, see:
- https://github.com/crossbeam-rs/crossbeam/pull/533
- https://twitter.com/khuey_/status/1311641831201857537
Quoting for posterity:
There is a 0.4.4 on a branch and it contains a reversion for the UB
mentioned in https://github.com/crossbeam-rs/crossbeam/pull/533.This was causing corruption of jemalloc structures (and ultimately a
deadlock) for us.
Update the crate resolving the issue.
Comment 2•4 years ago
|
||
I've been looking at the patch, the conversations on Twitter / GitHub and talked to Emilio on Slack.
It looks like there are no obvious pointers for how to turn that into a crash (or even an exploit).
The risk if this was exploited is sec-high (memory corruption), but I can hardly see us 0day ourselves here.
I'd suggest rating this sec-high as a precaution but also allowing for speedy sec-approval.
Tom, would you agree?
Comment 3•4 years ago
|
||
Your analysis sounds reasonable, I don't want to hold this up, so I'll defer to you =)
Assignee | ||
Comment 4•4 years ago
|
||
Comment on attachment 9178973 [details]
Bug 1668514 - Update crossbeam-channel. r=jrmuizel,janerik
Security Approval Request
- How easily could an exploit be constructed based on the patch?: pretty hard, it's not clear if possible even.
- 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?: 81,82
- If not all supported branches, which bug introduced the flaw?: Bug 1648405
- Do you have backports for the affected branches?: Yes
- If not, how different, hard to create, and risky will they be?: Trivial, not risky.
- How likely is this patch to cause regressions; how much testing does it need?: not very risky.
Beta/Release Uplift Approval Request
- User impact if declined: Potential weird crashes (unclear if possible)
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: none
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Simple dependency update to fix UB that can end up in memory corruption in some cases.
- String changes made/needed: none
Updated•4 years ago
|
Comment 5•4 years ago
|
||
(In reply to Frederik Braun [:freddy] from comment #2)
...
I'd suggest rating this sec-high as a precaution but also allowing for speedy sec-approval.
I set the wrong flag, oops.
Comment 7•4 years ago
|
||
Comment on attachment 9178973 [details]
Bug 1668514 - Update crossbeam-channel. r=jrmuizel,janerik
Approved, sorry
Comment 8•4 years ago
|
||
https://hg.mozilla.org/integration/autoland/rev/a853e285286d8d273b7bde64dcdca92474ce21c6
https://hg.mozilla.org/mozilla-central/rev/a853e285286d
Comment 9•4 years ago
|
||
Comment on attachment 9178973 [details]
Bug 1668514 - Update crossbeam-channel. r=jrmuizel,janerik
approved for 82.0b9
Comment 10•4 years ago
|
||
uplift |
Comment 11•4 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•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 13•4 years ago
|
||
Mostly copied their advisory, cleaned up grammar.
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
Updated•4 years ago
|
Description
•