AddressSanitizer: heap-use-after-free [@ nsRefreshDriver::Tick] with READ of size 8
Categories
(Core :: Graphics: WebGPU, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox75 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | fixed |
People
(Reporter: decoder, Assigned: kvark)
Details
(Keywords: crash, regression, reporter-external)
Attachments
(1 file)
12.14 KB,
text/plain
|
Details |
The attached crash information was submitted via the ASan Nightly Reporter on mozilla-central-asan-nightly revision 77.0a1-20200427214618-https://hg.mozilla.org/mozilla-central/rev/2b0e2483e2eaaef7ac49866a98e8e857520bdd5c.
For detailed crash information, see attachment.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Fairly sure this was fixed by https://phabricator.services.mozilla.com/rMOZILLACENTRAL7d6135dac2f270fa13ec7cea498b3c245de62ecc (which went in a day after the affected nightly was made).
Christian, is this still considered a security issue if it's on Nightly behind a pref the user has to turn on, enabling an experimental technology?
Updated•5 years ago
|
Reporter | ||
Updated•4 years ago
|
Comment 6•4 years ago
|
||
I was wondering if this was eligible for a bug bounty, since it was flagged sec-bounty
? This is my first time reporting a security issue, so I am unsure what I am supposed to do.
If it helps, the bug happened when I was running these WebGPU examples: https://austineng.github.io/webgpu-samples/, after reading this Mozilla Hacks article: https://hacks.mozilla.org/2020/04/experimental-webgpu-in-firefox/. I am happy to provide any other information you need.
Comment 7•4 years ago
|
||
(In reply to tdulcet from comment #6)
I was wondering if this was eligible for a bug bounty, since it was flagged
sec-bounty
? This is my first time reporting a security issue, so I am unsure what I am supposed to do.
You don't need to do anything. The bounty committee meets periodically and will decide whether or not this should receive a bounty.
Comment 8•4 years ago
|
||
This was certainly potentially eligible for a bounty, but it appears to have been a duplicate of a bug that was filed earlier and whose patch landed on the day this was filed. So unfortunately not this time, but please do keep submitting these!
Updated•1 year ago
|
Updated•6 months ago
|
Description
•