Closed Bug 1230253 Opened 9 years ago Closed 7 years ago

Crash in [@ nsGlobalWindow::SetDocShell ]

Categories

(Core :: DOM: Core & HTML, defect)

44 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox44 + wontfix

People

(Reporter: ritu, Unassigned)

Details

(Keywords: crash)

Crash Data

This crash signature is at #3 rank in 44.0a2 top-crashers category. It's a startup crash, affecting windows only and predominantly affecting version 44.0a2.
[Tracking Requested - why for this release]: Top crash on 44.0a2 and discussed in the channel meeting today.
Crash Signature: [@ nsGlobalWindow::SetDocShell ]
this seems to be caused by malware, as affected users all have a random {id}.xpi version 1.0.5781.6061 present in their modules (not extension!) list - the pattern is very reminiscent of bug 1181737 ... the first reports seem to have started in 44.0a1 build 20151029045227
Ritu, do you know who deals with blocklist these days? Could we block the relevant addon?
Flags: needinfo?(rkothari)
it's not an addon but a windows .dll masquerading as xpi-file. also its filename will be randomised/different on each infected system, so it isn't possible to blocklist based on that afaik...
(In reply to Olli Pettay [:smaug] from comment #4) > Ritu, do you know who deals with blocklist these days? Could we block the > relevant addon? Re-directing the question to Jorge who helps with addon blocks.
Flags: needinfo?(rkothari) → needinfo?(jorge)
If this is a DLL being injected directly into Firefox, there's nothing we can do in the add-on blocklist. I don't know who manages the in-product DLL blocklist. Maybe Kairo knows?
Flags: needinfo?(jorge) → needinfo?(kairo)
like the last time this happened (bug 1181737) the malware vendors seem to have fixed those crashes with an auto-update as the volume of the crashes is going back towards 0 now...
(In reply to Jorge Villalobos [:jorgev] from comment #7) > If this is a DLL being injected directly into Firefox, there's nothing we > can do in the add-on blocklist. I don't know who manages the in-product DLL > blocklist. Maybe Kairo knows? David Major did when he was still here, in recent weeks philipp has done some patches for DLL blocklist additions - and he already replied here :)
Flags: needinfo?(kairo)
Anything left to do in this bug, then?
Here is a reputable report on Yontoo: https://www.symantec.com/security_response/writeup.jsp?docid=2012-052923-1931-99 Only 1 crash in the last 7 days. I think philipp is right and the adware has gotten an update. Wontfix for 44.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.