GroupWise 6.5 Support Pack 6 Security Addendum

March 14, 2008

1.0 Client Shared Folder Security Issue

A security vulnerability exists in the GroupWise® Windows* client API that can allow programmatic access to non-authorized e-mail under certain conditions. The attacker must first authenticate to GroupWise and be a recipient of a shared folder from another user. The attacker could then exploit the vulnerability to gain unauthorized access to non-shared e-mail in the mailbox of the sharer.

Users who have shared folders with other users can protect their e-mail by removing shared access until remedial steps have been completed. It is not necessary to delete the contents of the shared folders and the folders can be re-shared after the administrator has locked out older client versions. To remove shared access to a folder in the GroupWise client, select the shared folder, click File > Sharing, then select Not Shared.

Administrators should lock out earlier versions of the GroupWise client in post offices where shared folders are in use.

  1. In ConsoleOne®, right-click the Post Office object, then click Properties.

  2. Click GroupWise > Client Access Settings.

  3. Select Minimum Client Release Date, specify March 9, 2008, then click OK.

  4. Repeat this procedure for each post office in your GroupWise system where shared folders are in use.

GroupWise 6.5 Windows client users should immediately update to GroupWise 6.5 SP6 Client Update 3 (dated March 11, 2008), in order to avoid being locked out of their post offices.

GroupWise 6.5 Cross-Platform client users should update to GroupWise 7 SP3 (dated March 11, 2008) as soon as their post offices have been updated to GroupWise 7. In the meantime, they should use the WebAccess client while the GroupWise 6.5 Cross-Platform client is locked out of their post offices.