Fixes for Mobile Phone Flaws
LG Incite users are still experiencing trouble with the SMS bug that I mentioned last week. There is good news and bad news for Incite folks: The good news is that AT&T has determined the problem's roots. The bad news is that the fix won't be available until February.
Apparently the trouble stems from the fact that the Incite sends SMS over GPRS, while AT&T sends SMS using either 3G networks or the more common GSM (but not EDGE). So if you're an Incite user in a 3G area, you should be able to send SMS. Otherwise, your options are fairly limited: Replace the Incite with another Windows Mobile phone, get a factory reset, or have AT&T remove your data plan, thereby pushing the phone back to GSM. No matter which method you use, February's fix can't come soon enough.
In other security news, RIM has released a software update that corrects several vulnerabilities with the BlackBerry Attachment Service's ability to handle specific PDF files. The patch prevents malicious code included in a PDF file from corrupting memory or launching code on the host computer. This affects versions of both BlackBerry Enterprise Server and BlackBerry Professional Software, and it could spread to networked computers. In the interim, RIM recommends that BlackBerry users only open attachments from trusted sources or prevent the Attachment Service from processing PDFs; you can find more information about prevention on BlackBerry's Web site.
Mac and PC users alike are vulnerable to Safari's recently-announced flaw. Mac users who haven't changed the default option for RSS readers to Safari are at risk as the flaw could allow sensitive data (including passwords and log-in info) on the user's computer to be read. While Mac users may be able to prevent this problem by simply switching the default RSS reader, Brian Mastenbrook's most recent post on the issue indicates that the best solution now involves third-party software. Windows Safari users are likely better off using another browser until the issue has been properly fixed.
While this one is currently minor, being on the safe side is always advisable. Apple is said to be aware of the problem, but there are no details as yet on a patch.