Crash in [@ mozilla::dom::MessageChannel::~MessageChannel]
Categories
(Core :: DOM: postMessage, defect)
Tracking
()
People
(Reporter: jesup, Assigned: jstutte)
Details
(Keywords: crash, csectype-uaf, sec-high)
Crash Data
UAFs with e5e5 addresses in ~MessageChannel, called from CC
Updated•3 years ago
|
Comment 1•3 years ago
|
||
This is actually about the DOM API MessageChannel, not the IPC MessageChannel. The cycle collector appears in the stack just because it always does when we delete cycle collected objects.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
There are 3 reports in the last 6 months, all from the same install time. The URL of the crash is WhatsApp.
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
|
||
I see always only that 3 crashes from the same install and same beta-version on Windows 7. Randell, is this really worth a sec-high rating?
| Reporter | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 4•3 years ago
|
||
We do not have any actionable information but want to monitor this for a while before marking it stalled.
Comment 5•3 years ago
|
||
Given that this only happened once as far as we can see, I'd just mark it incomplete if it doesn't come up again.
| Assignee | ||
Comment 6•3 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #5)
Given that this only happened once as far as we can see, I'd just mark it incomplete if it doesn't come up again.
Yes, no more reports and those occurred where all from the same beta install on the same day, so not even from a shipped release.
Updated•1 year ago
|
Description
•