538775 - Firefox Crash [@ VEngine.dll@0x516c ] comodo verification-engine

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Comodo AV, defect)

Description

[chris hofmann]

#22 in very early 3.6 rc1 data, but it appears to have been around awhile.

this might be the same problem posted in support forum 
http://forums.comodo.com/verification_engine_cve/constant_crashes_of_firefox_after_vengine_27024_upgrade-t43735.0.html

for this product

http://www.comodo.com/home/internet-security/verification-engine.php

stack looks like

http://crash-stats.mozilla.com/report/index/b781b1ec-412a-49a6-a64a-ca3c42100109

Frame  	Module  	Signature [Expand]  	Source
0 	VEngine.dll 	VEngine.dll@0x516c 	
1 	VEngine.dll 	VEngine.dll@0x80c1 	
2 	VEngine.dll 	VEngine.dll@0x50183 	
3 	VEngine.dll 	VEngine.dll@0xc72b

more reports at

http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=VEngine.dll%400x516c&version=Firefox%3A3.6

checking --- 20100108-crashdata.csv VEngine.dl
release total-crashes
              VEngine.dl crashes
                         pct.
all     212980  26      0.000122077
3.0.15  2056            0
3.0.16  8335            0
3.5.5   5677            0
3.5.6   26670   1       3.74953e-05
3.6     1758    20      0.0113766
3.6b5   22218   5       0.000225043
3.6b4   1646    2       0.00121507
3.6b3   627             0
3.6b2   731             0
3.6b1   2047            0

other signatures might also be related.

signature list
   9 VEngine.dll@0x516c
   8 VEngine.dll@0x505c
   3 VEngine.dll@0x4dec
   3 VEngine.dll@0x1a9ee
   2 VEngine.dll@0xe348
   1 VEngine.dll@0x813b

anyone have a contact at comodo that can have a look?

v engine provides no version info in the .dll, so we should try to get that fixed at a minimum.

Comment 1

[Robin Alden]

I've passed it on internally and will report back.

Regards
Robin

Comment 2

[timeless]

thanks :)

Comment 3

[Marcia Knous [:marcia]]

http://forums.comodo.com/verification-engine-cve/firefox-36-rc1-crash-with-ve-27033-t49763.0.html;msg357242 has some information as well.

Comment 4

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.

Comment 5

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.