First published: Wed May 14 2014(Updated: )
Android OS before 2.2 does not display the correct SSL certificate in certain cases, which might allow remote attackers to spoof trusted web sites via a web page containing references to external sources in which (1) the certificate of the last loaded resource is checked, instead of for the main page, or (2) later certificates are not checked when the HTTPS connection is reused.
Credit: vultures@jpcert.or.jp
Affected Software | Affected Version | How to fix |
---|---|---|
Android | <=2.1 | |
Android | =1.0 | |
Android | =1.1 | |
Android | =1.5 | |
Android | =1.6 | |
Android | =2.0 | |
Android | =2.0.1 | |
<=2.1 | ||
=1.0 | ||
=1.1 | ||
=1.5 | ||
=1.6 | ||
=2.0 | ||
=2.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4832 is classified as a high severity vulnerability due to the risk of SSL certificate spoofing.
To mitigate CVE-2010-4832, upgrade your Android OS to version 2.2 or later.
CVE-2010-4832 can allow remote attackers to impersonate trusted websites, potentially compromising user data.
CVE-2010-4832 affects Android versions prior to 2.2, including versions 1.0 through 2.1.
CVE-2010-4832 is primarily a client-side vulnerability affecting the way Android handles SSL certificates.