Yet another 0day for IE Sep 19 2006 05:51AM
Gadi Evron (ge linuxbox org)
Sunbelt Software released a warning on a new IE 0day they detected
in-the-wild, to quote them:
"The exploit uses a bug in VML in Internet Explorer to overflow a buffer
and inject shellcode. It is currently on and off again at a number of
Security researchers at Microsoft have been informed. This story is
developing and research is ongoing. Security professionals can contact
me for collaboration or further information. This exploit can be mitigated
by turning off Javascripting."

They also notified some closed and vetted security information sharing
groups on the matter, with further details. You can find their blog entry

That's that.

Why do I call it a 0day? Because it has indeed been used in-the-wild
before it was publicly discovered. People are CURRENTLY and for a while
now, being exploited.

Lately we call every exploit being released in full disclosure mode a
0day. That's a 1-day or at least it has to be from now on, as there are
just too many of those and there are more to come.

This trend started with Websense detecting an IE 0day (not really IE
- WMF) used in-the-wild by spyware, to infect users.
"Responsible disclosure" is important, but when it takes so long to get a
response or a fix with "Irresponsible vendors", and with so much money to
be made by not disclosing vulnerabilities at all - it is becoming
passe. New exploits don't need to be gleamed from patches or feared in
full disclosure. Someone just pays for a 0day.. it's their business and
they invest in it.

1. Lots more coming.
2. Please call it a 1-day if it's full disclosure mode, and 0day if it
has been seen in-the-wild.

The motivation has now moved from "let's be responsible" or "let's have
fun" to "let's make money" or "let's stop waiting and be mocked by
irresponsible vendors". This is not about everybody, it's about how things are.

Even idefense and zdi can't pay enough when compared with people who make
money from what the 0day gives them - exploited users and a money making



[ reply ]


Privacy Statement
Copyright 2010, SecurityFocus