ZipperDown Vulnerability Could Hit 10% of iOS Apps
A newly discovered vulnerability could affect thousands of iOS apps -- and Android users may not be spared.
A newly announced vulnerability in iOS (and, just maybe, Android) could be an avenue for exploitation through misbehaving apps. The vulnerability, named "ZipperDown" by Pangu Lab, is described as a "common programming error" by the researchers — so common, in fact, that the team estimates 15,978 out of 168,951 iOS apps (or nearly 10% of the total) are affected.
So far, Pangu Lab has not released details of the vulnerability to the public, though they are working with app publishers thought to be affected. The good news is that ZipperDown seems to require at least a couple of unusual conditions for an exploit to occur: The first is that the attacker must control the WiFi network to which the device is connected. Next, the app in question must be running outside the iOS "sandbox."
If those two conditions are met and the vulnerability is exploited, it could allow a hacker to run illicit applications on the affected device. While an Android vulnerability to the issue has not been formally confirmed, Pangu Lab says that the conditions for exploit exist and they will issue an additional report in the near future.
While the conditions for successful exploit are limited, the sheer number of apps affected make this a vulnerability developers are taking seriously in spite of (or perhaps due to) its name.
Pangu Lab has released a video showing the exploit:
Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
Enterprise Vulnerabilities From DHS/US-CERT's National Vulnerability DatabaseCVE-2018-12580 PUBLISHED: 2018-06-19
library/DBTech/Security/Action/Sessions.php in DragonByte vBSecurity 3.x through 3.3.0 for vBulletin 3 and vBulletin 4 allows self-XSS via $session['user_agent'] in the "Login Sessions" feature.
The web console login form in ovirt-engine before version 4.2.3 returned different errors for non-existent users and invalid passwords, allowing an attacker to discover the names of valid user accounts.
An issue was discovered in Zuul 3.x before 3.1.0. If nodes become offline during the build, the no_log attribute of a task is ignored. If the unreachable error occurred in a task used with a loop variable (e.g., with_items), the contents of the loop items would be printed in the console. This could ...