Interesting time line:
2009/04/07 Identification of the vulnerability.
2009/04/23 Notification of IBM via the customer.
2009/04/23 Technical knowhow exchange between scip AG/IBM.
2009/06/05 Asking for current status by scip AG. (no answer)
2009/07/09 Asking for current status by scip AG.
2009/07/09 Reply with current status and assigned PMR.
2009/08/24 Asking for current status by scip AG. (no answer)
2009/09/08 Public disclosure of the advisory.
Published by IBM today. If you need to fix, you have to contact IBM Support.
this might be a stupid question but if you have to log a call wont you need a support contract ? or does that not apply to security fixes
Another stupid question - HTML formatted emails are rendered by Internet Exploder too.
That must also be done in the local context. If you have ever printed an HTML email from Notes 8+ you will know that you get the standard IE print header and footer complete with the local URL in the footer.
Someone please tell me there isn't a code execution possibility right there.
Best bet is to open a call and find out. (I am not sure if you can or not). Either way there are 3 other options you can do in the meantime.
By the way. The Technote was not published today (only updated today). It was posted before scip AG posted the exploit publicly.
@Chris - Actually, HTML formatted emails as "cleaned up" first to prevent malicious code. The cleanup may not be perfect, but it is a different scenario.
@Ben is that clean up exactly documented somewhere?
I fear you are both missing the point. The problem is that the Notes RSS reader, dumps the HTML into a local file on the user's PC. When IE is then invoked to render that local file, it does so outside its sandbox.
When IE, as a browser, renders HTML received from an HTTP source, it does so in its sandbox. Now one could argue about how effective that sandbox is, but that is a whole other issue!
@Nick: Neither Chris nor Ben talked about HTML from an HTTP source, but from HTML included in formatted mails from outside. I think it's not too unlikely the same happens with them.
But BTW: isn't that what every other local RSS reader application would do?
No, they don't. It's a very basic design failure. Other feed readers like FeedDemon use the proper Internet sandbox.
If you start digging around in the "standard" client outside of what used to be Notes, you will find lots of stuff that will lead to more security discussions. Code signing, ECL etc don't exist there. And you are supposed to turn malware protection off in this space, so that performance does not suffer.
Well, who's to bless & who's to blame ? One of the biggest questions on opening the Notes Client to the Eclipse platform for me was about security of plugins. The monolitic C++ Notes Client was much less vulnarable to lazy programmers than the open Eclipse platform is. That IBM itself had to prove that is some sort irony to me. Eclipse is a blessing and a curse - flexibilty and openness always means responsibility... . And - don't get me wrong - even with this, I appreciate the way, IBM is heading with Notes 8.x, Eclipse and Expeditor.
It's probably a matter of trust. If you want to use widgets, you have to trust them. If you can't trust a plugin from IBM, whom do you want to trust? The RSS widget is a perfect malware dropper. Access to the local file system, ability to run processes in user space.
@Vowe: So when I use a feedreader with offline capabilities (I think most of the popular do), I would load the HTML from the local file system as well?
Lotus Notes RSS reader is a joke anyway.
Volker Weber on Outlook for iOS and Android is now fully powered by the Microsoft Cloud at 13:45
Sven Rohweder on Outlook for iOS and Android is now fully powered by the Microsoft Cloud at 13:29
Oliver Stein on Nächste c't: EMM für alle at 13:15
Chris Lindley on It's a tight race for udoq at 13:11
Volker Weber on Outlook for iOS and Android is now fully powered by the Microsoft Cloud at 13:11
Sven Rohweder on Outlook for iOS and Android is now fully powered by the Microsoft Cloud at 13:08
Volker Weber on Nächste c't: EMM für alle at 12:42
Oliver Stein on Nächste c't: EMM für alle at 12:39
Jörg Hermann on Warten auf die Telekom at 11:13
Patrick Bohr on Warten auf die Telekom at 09:46
Volker Weber on Sonos coming to the Apple Store at 09:06
Thomas Meyer on Sonos coming to the Apple Store at 08:56
Volker Weber on Sonos coming to the Apple Store at 03:40
Philipp Münzel on Sonos coming to the Apple Store at 03:39
Jonas Rathert on Sonos coming to the Apple Store at 23:59
Felix Binsack on Observations from using the new iPhone and Watch at 23:20
Abdelkader Boui on Nächste c't: EMM für alle at 22:45
Jason Mason on Kurswechsel bei IBM at 22:17
Volker Weber on Sonos coming to the Apple Store at 22:15
Peter Meuser on Sonos coming to the Apple Store at 22:01
Peter Meuser on Outlook for iOS and Android is now fully powered by the Microsoft Cloud at 21:58
Hubert Stettner on Nächste c't: EMM für alle at 21:52
Mariano Kamp on Sonos coming to the Apple Store at 20:39
Hubert Stettner on Warten auf die Telekom at 20:11
Volker Weber on Warten auf die Telekom at 19:25