1. /
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Norton Mobile Security Beta Information Disclosure

SYM10-011

November 11, 2010

Revision History

none

Severity

Medium

Remote Access With user interaction
Local Access No
Authentication Required Yes (access granted by user in most cases)
Exploit publicly available Proof of Concept

Overview

Symantec’s Norton Mobile Security Beta for Android logs information to the Android Smartphone system logs. Inadvertent or malicious access to logs could allow potentially sensitive user and application information to be revealed.

Product(s) Affected

Product Version Solution
Norton Mobile Security Beta for Android 1.0 Beta Release Upgrade to Norton Mobile Security 1.5 Beta

Details

Android system logs where Norton Mobile Security Beta sensitive information is stored. Some applications downloaded to an Android Smartphone may be able to gain unnecessary and/or unauthorized read/write access permission to device logs without the consent or knowledge of the device owner.

An individual could potentially create a malicious application that can gain unauthorized access to sensitive Norton Mobile Security Beta information stored on device system logs. An attacker would have to effectively entice the user to download the hostile app by visiting a malicious web site or by clicking on a malicious URL. The user would need to authorize the permissions required and requested by the app in most instances though the app may be able to circumvent actual user authorization is some instances.

Such an attack could potentially expose application setup information to possibly include the wipe/lock credentials the user established for the Norton Mobile Security Beta application. This could possibly result in a malicious user being able to be able to deny the user access to the phone or potentially manipulate personal data stored on the phone via specifically formatted messages.

Symantec Response

Symantec product engineers have developed and released a solution. Symantec Mobile Security Beta for Android users should updated to the latest release available through normal update procedures.

Symantec knows of no exploitation of or adverse customer impact from this issue.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Keep Smartphone operating systems and applications updated with the latest vendor patches
  • Run an anti-malware application to provide detection and protection to both inbound and outbound threats
  • Users should be cautious of unknown applications or applications from sites they are not familiar with or of questionable reputation
  • Be wary of attachments and executables delivered via email or IM and be cautious of browsing unknown/untrusted websites or clicking on unknown/untrusted URL links
  • Be aware of and understand the impact of permissions being requested by the app being download before granting access

Credit

Symantec thanks Tim Wyatt with Lookout Mobile Security for reporting their finding and coordinating closely with Symantec in resolving the issue.

References

Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 44767 to this issue for inclusion in the Security Focus vulnerability database.

This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org). The CVE initiative has assigned CVE-2010-0113 to this issue.
Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: November 11, 2010
Security Response Blog
The State of Spam