Open Handset Alliance Android Privilege Escalation Vulnerability



Date Discovered

April 21, 2011


Open Handset Alliance Android is prone to a privilege-escalation vulnerability because it fails to properly handle certain socket messages. Successfully exploiting this issue can allow attackers to corrupt memory and execute arbitrary code with superuser privileges, leading to a complete compromise of the device.

Technologies Affected

  • Open Handset Alliance Android 2.0
  • Open Handset Alliance Android 2.0.1
  • Open Handset Alliance Android 2.1
  • Open Handset Alliance Android 2.1.1
  • Open Handset Alliance Android 2.2
  • Open Handset Alliance Android 2.3
  • Open Handset Alliance Android 2.3.1
  • Open Handset Alliance Android 2.3.2
  • Open Handset Alliance Android 3.0
  • Open Handset Alliance Android


Run all software as a nonprivileged user with minimal access rights.
To limit the potential damage that a successful exploit may achieve, run all nonadministrative software as a regular user with the least amount of privileges required to successfully operate.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Do not allow untrusted users physical access to systems.
Users should not allow unknown or untrusted users to access affected devices.

Vendor updates are available. Please see the references for more information.



The Android Exploid Crew

© 1995- Symantec Corporation

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


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 Security Response, and 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.