»

[mikeymike]

I'm trying to find a good article that is reasonably up-to-date, which includes information like what patches stopped certain security holes in MS mail software, and what its current status is at the moment (ie. what a fully-patched system is vulnerable to).

And no, I'm not considering going back to using Outlook / Express :-)

[Vincent]

mikeymike wrote:
And no, I'm not considering going back to using Outlook / Express :-)

You just want to laugh at how many holes there are/were? ;-)

[mikeymike]

No, advising a customer. I am aware of the general issues with running MS mail clients, but having some solid facts and research to hand would be useful.

[Jettah]

Vincent wrote:

You just want to laugh at how many holes there are/were? ;-)

Ehm, isn't then Outlook / Express a hole by itself?

On the other hand, consider that it is part of M$'s .NET strategy and a net isn't that just a bunch of holes tied together with pieces of rope? :-P

I know, you arn't getting any the wiser from this reflections, but think of the fun, ehm, well eh fun?

Cheers

Tjitte

[Cass]

Go check this, and customize your search according to your needs.
________
Shemale Amateur

[mikeymike]

Thanks. I had looked there already, but it's not easy to differentiate between what are classed as IE vulns and strictly O/OE vulns.

[Trev]

You won't find many patches specific to Outlook or Outlook Express. When patches are released, they're usually pacakaged as an Office or Internet Explorer patch, repsectively. I wouldn't necessarily call the problems with either product vulnerabilities. In many cases, the vulnerabilities have more to do with a user's understanding of the product than the product itself (i.e. not disabling preview, launching attachments from unknown senders, etc.).

That said, you'll need to hit the security site mentioned above and search for Office (all versions), Outlook (all versions), Outlook Express (all versions), and Internet Explorer (all versions). Again, you won't find many patches specific to the mail clients. What you'll see are things like, "added switch to enable users to disable HTML previews," and such.

As with any software product, your customers should understand the features available in the product, the risks associated with using those features, and how to mitigate those risks.

Trev