Crash in memset | sftk_DestroySessionObjectData
Categories
(NSS :: Libraries, defect, P3)
Tracking
(firefox-esr52 wontfix, firefox58 wontfix, firefox59 wontfix, firefox60 wontfix)
People
(Reporter: philipp, Unassigned)
References
Details
(Keywords: crash, csectype-uaf, sec-high, Whiteboard: [sec-triage-backlog] )
Crash Data
Updated•7 years ago
|
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Updated•7 years ago
|
Comment 5•7 years ago
|
||
Comment 6•6 years ago
|
||
This is most likely also due to improper refcounting on destruction like Bug 1508776. All sftk
types are similarly constructed.
Comment 7•6 years ago
|
||
Now that we've solved Bug 1508776 I am more sure that this is a much-the-same issue, but I haven't yet ascertained if the same solution will apply. I'll be thinking on it.
Updated•6 years ago
|
Comment 8•5 years ago
|
||
JC: can we close this bug worksforme now? Although clearly a UAF, most of the ongoing crashes are in ESR-52 -- the stranded WinXP/Vista folks. The bug is still present in ESR-60 and in the last 6 months two people hit the crash on Fx 61. No crashes in anything more recent than that. Something fixed it, but it wasn't bug 1508776 since it looks like that didn't land until ~Fx70.
Comment 9•5 years ago
|
||
Good plan. Works For Me.
Comment 10•5 years ago
|
||
Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit auto_nag documentation.
Comment 11•5 years ago
|
||
Removing employee no longer with company from CC list of private bugs.
Updated•2 years ago
|
Description
•