Michael Sutton
Michael Sutton
directly effort further latest loyal pay people programs reward various
We pay people directly for their submissions, and then we also have various programs to reward our loyal contributors and keep them working with us. This is our latest effort to further reward them.
aware code exploit public
We're not aware of any public exploit code for it at this time.
america applaud compass decision food group healthy major market north ocean seafood similar step support toward ways
We applaud Compass Group North America for its leadership. Its commitment, and a similar decision by major food retailer Wal-Mart, is a significant step toward transformation of the seafood market in ways that support sustainable fisheries and healthy ocean ecosystems.
drank drinking
He wasn't even drinking or anything. Never drank before.
certainly code exploit implement patch recommend until users
I would certainly recommend that users implement the vendor workarounds until a patch is made available. We feel that exploit code can and will be created.
capability code create default difficult display exploit generally image instead media page player public render ripe target though uses web windows
Even though Windows Media Player is not something generally used to render images, it has the capability of doing that. It's not difficult to create a Web page that uses Windows Media Player to display an image instead of the default application. I think it's a ripe target for exploitation if we see public exploit code for it.
both front identify major rewards secure valuable
Many of our most valuable contributors consistently identify significant vulnerabilities that may never make the front page, but both avert major exploitation and secure considerable compensation through our rewards program.
champions ocean potential
Ocean Champions has the potential to be one of the most transformative things we've ever done in the whole conservation movement.
code free information model pay quite researcher review wants
The only model that makes no sense to me is the altruistic model. The vendor wants the researcher to do his code review for free and that doesn't quite fly. They are profiting from the vulnerability information but they don't want to pay for it.
apply code developers entire good level pieces relying security shared testing using writes
There's always code reuse in development, which is a good thing. No one writes an entire application from scratch. But if you're using someone else's code, you're relying on the security of that code. Developers need to apply the same level of security testing to those shared pieces as they do to their own code.
canned default include vulnerable
A DLL is canned functionality, so if you include a vulnerable DLL in an application, that application is by default vulnerable.
degree draw easy file full further hard leverage malicious people relatively site social takes web
This is relatively easy to exploit. It takes some degree of social engineering -- the attacker would have to draw people to a malicious Web site -- but after that, there's no further intervention required. An attacker could leverage this to write to a file on the hard drive. And once you can write to a person's machine, you have full control.
code expect exploit public
Patching is very urgent. We expect public exploit code to become available, especially for the MSDTC issue.
code expect exploit public
Patching is very urgent, ... We expect public exploit code to become available, especially for the MSDTC issue.