Just in case you thought there wasn't going to be further updates to GW BES


New fixes include:
*When BlackBerry device users searched for messages on their devices, the
BlackBerry Messaging Agent added many lines to its log file (for example,
"[20000] (11/04 16:17:41.888):{0x1B18} PMDatabaseSQLImp::GetMbMailSyncItem,
Table MBMailSync; item not found (userid 12)"). These lines might have
filled up the Event Viewer in Windows and overwritten events that were not
related to the BlackBerry Enterprise Server. (DT 1029358)

*The BlackBerry Enterprise Server was potentially prevented from
automatically regenerating the device transport key. The user could
regenerate the encryption key manually, as a workaround. The BlackBerry
Enterprise Server now regenerates the device transport key automatically.
(DT 1020903)

*If you moved a user account from BlackBerry Enterprise Server 4.1 SP6 or
higher to 5.0 SP1 using the BlackBerry Enterprise Transporter, the
BlackBerry Policy Service might not have been able to regenerate encryption
keys and the device might not have been able to send or receive data. (DT

*When you activated users on the BlackBerry Enterprise Server the management
logs grew at an unexpectedly high rate. (DT 730098)

Security Update:

*A security vulnerability existed in the PDF distiller of the BlackBerry
Attachment Service. This vulnerability could have allowed a malicious
individual to cause buffer overflow errors, which might have resulted in
arbitrary code execution on the computer that hosts the BlackBerry
Attachment Service. While code execution was possible, an attack was more
likely to result in the PDF rendering process terminating before it
completed. In the event of such an unexpected process termination, the PDF
rendering process restarted automatically but did not resume processing the
same PDF file.

Successful exploitation of this issue required a malicious individual to
persuade a device user to open a specially crafted PDF file on a device that
was associated with a user account on a BlackBerry Enterprise Server. The
PDF file might have been attached to an email message, or the device user
might have retrieved it from a web site using the Get Link menu item on the
device. (DT1038261)

This issue was resolved in an earlier interim security