Exploit mitigated with Firefox 46
Hello: Yesterday, I updated Firefox to version 46 and was noticing some choppiness with page loading afterward but nothing alarming. This day, I was logging into gmail and Firefox was automatically closed by my security program with a DEP mitigation logged in Event Viewer. The browser had one theme add-on (since removed) and AdBlocker Ultimate. I uninstalled Firefox and reinstalled it.
The machine has Windows 10, version 10856.218, which I believe is current. What made Firefox vulnerable to this kind of exploit? If there's something I neglected to do or if there's something that needs to be done, please tell me so that I can do it immediately.
No malware apparently made it on here, which is good. I tried to upload a screenshot of the mitigation details but the loading circle kept spinning around and around. If there's an alternate way to get this information to you, I'll do it.
Thanks for any insight/assistance with this serious matter.
Выбранное решение
Yeah, here:
http://www.wilderssecurity.com/threads/hitmanpro-alert-support-and-discussion-thread.324841/page-382
Looks like a false positive, again.
How could anyone have known this in advance, this is buried under mounds of text in some obscure forum somewhere.
Personally, I'm ready to ditch this HMP-A thing, it's conflicted with every major program on my machine, freezing my firewall solid for hours and I didn't have a clue as to what was going on.
I couldn't understand why Firefox would have a vulnerability like that in its latest version, and it seems it really doesn't. So for now, this issue is resolved, unless there's additional pertinent info about this stupid matter. Firefox is great, wouldn't use anything else.
Прочитайте этот ответ в контексте 👍 0Все ответы (5)
Wait a minute, after looking around, I found a small "bug" article concerning HitmanPro Alert and Firefox version 46.0. Is this the issue? I sure hope so because what little I could glean about these types of exploits sure wasn't pretty.
Strangely, immediately following the above mitigation, HMP-A installed an update to its latest build, something that hasn't been done in nearly a month. So yeah, I'm leaning toward the "bug" explanation.
To modify my above post, after initially installing version 46, Firefox crashed. I generated a crash report, sent it to Mozilla and reserved it in the browser, so it's there upon request.
Thanks, any info that's needed, I'll supply it.
Hitman has caused many issues in the past for Firefox. Disable or update it.
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.
As I stated previously, HMP-A was automatically updated right after this mitigation notice which indicates to me there's some kind of telemetry associated with this particular conflict. I'm not disabling it but I'm not pleased with the ongoing conflicts either; this isn't the first time.
https://crash-stats.mozilla.com/report/index/8881d1cf-7941-47ed-a3fc-a0c742160501
Your method for copy/paste of crash report didn't work, there's only one report, generated on 4/30/2016. If there's another way, let me know.
I can understand if a conflict between Firefox and HMP-A would cause the browser to crash but I don't understand how a "DEP mitigation" would be generated from this conflict.
Выбранное решение
Yeah, here:
http://www.wilderssecurity.com/threads/hitmanpro-alert-support-and-discussion-thread.324841/page-382
Looks like a false positive, again.
How could anyone have known this in advance, this is buried under mounds of text in some obscure forum somewhere.
Personally, I'm ready to ditch this HMP-A thing, it's conflicted with every major program on my machine, freezing my firewall solid for hours and I didn't have a clue as to what was going on.
I couldn't understand why Firefox would have a vulnerability like that in its latest version, and it seems it really doesn't. So for now, this issue is resolved, unless there's additional pertinent info about this stupid matter. Firefox is great, wouldn't use anything else.
That was very good work. Well Done.