BlackBerry-maker Research In Motion (RIM) yesterday issued two separate security advisories warning both BlackBerry smartphone users and corporate BlackBerry Enterprise Server (BES) administrators of newly discovered security flaws in many versions of RIM’s BlackBerry handheld software and in BES.
The first advisory applies to BlackBerry smartphone users, and it warns of what RIM is calling a “partial Denial of Service (Dos)” attack, in which websites with hidden malicious code could potential freeze up users’ BlackBerry Browsers and render them unable to surf the Web until the browser either restarts itself or the device is rebooted.
From RIM:
“This advisory relates to a BlackBerry Device Software vulnerability that could allow an attacker to maliciously craft a web page such that, when the BlackBerry device user views the page on a device running the affected BlackBerry Device Software, the browser application becomes unresponsive….Successful exploitation of this issue relies on the user viewing the maliciously crafted web page on a device running the affected BlackBerry Device Software.”
The flaw ranks as “medium” severity on the Common Vulnerability Scoring System (CVSS), and RIM says it has issued updated BlackBerry handheld software to solve the problem. The vulnerability doesn’t exactly require an urgent fix since the worse that will happen is an affected user’s browser might freeze up. But RIM says any and all BlackBerry users running handheld software version 5.0.0 to 6.0.0 should check their wireless carrier’s websites or BlackBerry.com for software updates. BlackBerry handheld software prior to v5.0.0 is not supported and software newer than v6.0.0 is not affected, according to RIM.
Related stories
Top 5 ways to keep your BlackBerry secure
Government BlackBerries a security risk: privacy commissioner
(Note: Even if RIM has pushed software updates to wireless carriers to address the issue, it often takes those carriers time to examine and approve the software. If no update is currently available for your device, and you find your browser freezing up, RIM suggests simply waiting until the problem resolves itself or resetting your BlackBerry by removing its battery.)
The last major BlackBerry-Browser-related security flaw identified by RIM was in September of 2009.
The second BlackBerry security advisory released yesterday relates to yet another flaw in the PDF Distiller component of RIM’s BlackBerry Enterprise Server. Issues with the troublesome BES PDF distiller have been identified as “severe” risks in at least five different RIM security advisories since the summer of 2008.
From RIM:
“The vulnerability could allow a malicious individual to cause buffer overflow errors, which may result in arbitrary code execution on the computer that hosts the BlackBerry Attachment Service. While code execution is possible, an attack is more likely to result in the PDF rendering process terminating before it completes. In the event of such an unexpected process termination, the PDF rendering process will restart automatically but will not resume processing the same PDF file.”
“Successful exploitation of this vulnerability requires a malicious individual to persuade a BlackBerry smartphone user to open a specially crafted PDF file on a BlackBerry smartphone that is associated with a user account on a BlackBerry Enterprise Server. The PDF file may be attached to an email message or the BlackBerry smartphone user may retrieve it from a web site using the BlackBerry Browser.”
This latest security advisory has highest CVSS score I’ve seen tied to any such BlackBerry warning, 9.3 out of 10, with 10 representing the most severe threats. RIM says any and all BlackBerry administrators running full BES, BES Express or BlackBerry Professional Software for Microsoft Exchange, IBM Lotus Domino or Novell GroupWise should visit its server downloads page to see if a security update is available.
For more information on the partial DoS attack that could affect BlackBerry smartphone users or the newly identified BES vulnerability, visit RIM’s advisory pages here and here, respectively.
