gilahank@mcbrides_resources:~# session --user=student_
[ HOME ] [ CONNECTION: SECURE ]
gilahank@mcbrides_resources:~/apple-google-security# cat readme.txt

Apple & Google Security

A comparison of security between the two major mobile operating systems.

On This Page

Smart Phone Market Share

Market share matters for security: attackers go where the users are. Android dominates worldwide, while iPhone leads in the U.S.

$ cat ./us-market-share-by-year.tsv — United States
YeariOS Market Share (%)Android Market Share (%)
202059.5440.27
202158.5841.11
202256.7442.94
202358.141.46
202458.8140.81
202558.4441.28
$ cat ./market-share-by-region.tsv
RegionAndroid (%)iOS (%)Other (%)
Worldwide75.1824.440.38
Africa87.4711.381.15
Asia83.0916.380.53
Europe66.8432.630.53
North America43.6756.240.09
Oceania54.9144.740.35
South America88.5611.170.27

Apple Security

Apple’s App Store

Apple has a rigorous App Review system that screens every app and update before it goes live on the App Store. This process includes:

  • Automated scans for malware, suspicious behavior, and policy violations.
  • Human review for content, functionality, and compliance with App Store guidelines.
  • Developer identity verification to prevent fraudulent submissions.

Because of this, many malicious apps are blocked before they ever reach users. For example:

  • In 2025, Apple rejected more than 2 million app submissions, out of over 9.1 million reviewed.
  • In 2024, Apple rejected about 1.93 million submissions and removed 82,509 apps that were already on the App Store.
  • In 2024, Apple also blocked more than 10,000 illegitimate apps on pirate storefronts (28,000 in 2025).
$ cat ./apple-app-review.tsv — Apple’s annual fraud-prevention reports
YearSubmissions RejectedRemoved After ListingPirate-Storefront Apps Blocked
2022~1.7 millionnot reported~57,000
20231.7 million+not reported47,000+ *
2024~1.93 million82,50910,000+
20252 million+not reported28,000

* Apple reported 47,000+ for the 12 months before May 2024. Apple only published a count of apps removed after listing for 2024.

Lessons for users: Most malicious apps are blocked before publication thanks to Apple’s review process. But some still get through and are removed later (82,509 in 2024), so users may have installed them before they were flagged. SparkCat (below) passed App Review.

iOS Exploits

Each entry includes the likelihood that a typical user would be exposed.

$ cat ./ios-exploits.tsv — major iOS exploits, oldest first
YearExploit / CVEExploit TypeLikelihoodNotes
2007–2011JailbreakMe 1.0–3.0Safari vulnerabilities (a TIFF image bug in 1.0; PDF/font bugs in 2.0–3.0)LowRequired the user to visit a specific website; mostly used for jailbreaking. Patched quickly by Apple.
2016Pegasus Spyware (“Trident”)
CVE-2016-4655, CVE-2016-4656, CVE-2016-4657
Zero-day exploit chainLow to ModerateTargeted high-profile individuals; required a link click but was very stealthy.
2019Checkm8Bootrom exploit (hardware-level; cannot be patched by software updates)LowRequired physical access to the device; used mainly for jailbreaking older iPhones (A5–A11 chips).
2021FORCEDENTRY
CVE-2021-30860
Zero-click iMessage exploitModerate to HighNo user interaction needed; used by NSO Group’s Pegasus spyware in targeted surveillance campaigns.
2022CVE-2022-42827Kernel out-of-bounds writeLowLet an app run code with kernel privileges; Apple reported it may have been actively exploited. Required a malicious app or a chain with other exploits; patched in iOS 16.1.
2023CVE-2023-28206IOSurfaceAccelerator kernel vulnerabilityLowA zero-day chained with a WebKit bug (CVE-2023-28205) in targeted spyware attacks; unlikely to affect typical users who keep iOS updated.
2024CVE-2024-23222WebKit remote code executionModerateCould be triggered by visiting a malicious website; fixed by iOS/Safari updates.
2025SparkCat MalwareScreenshot/photo data theft via OCR (optical character recognition)Low to ModerateThe first known OCR-based stealer found in Apple’s official App Store (also in Google Play, 242,000+ downloads there). Infected apps asked for photo access, then scanned images for crypto-wallet recovery phrases and other text.

Google Security

Google’s Play Store

Policy-violating apps Google prevented from being published, by year:

$ cat ./google-play-blocked.tsv — Google’s annual Play safety reports
YearApps Blocked Before ListingDeveloper Accounts Banned
20221.43 million173,000
20232.28 million333,000
20242.36 million158,000
20251.75 million+80,000+

Google does not publish a yearly count of apps removed after listing. It credits the 2025 drop to stronger deterrence, with fewer bad actors attempting to publish.

Lessons for users: Don’t trust apps just because they’re on the Play Store. Avoid installing apps via ads — always search and download directly. Check app permissions and reviews before installing. Use Play Protect and keep your device updated. Use virus protection.

Android OS Exploits

Each entry includes the likelihood that a typical user would be exposed.

$ cat ./android-exploits.tsv — major Android exploits, oldest first
YearExploit / CVEExploit TypeLikelihoodNotes
2008CVE-2008-7298Cookie forcing via the Android browserLowAllowed attackers to overwrite or delete cookies in HTTPS sessions due to lack of HSTS enforcement. Required a man-in-the-middle attack; mitigated in later versions.
2010RageAgainstTheCageadb daemon privilege escalationLowUsed to gain root access through the Android Debug Bridge. Required USB debugging and physical access; mostly used for rooting.
2011GingerBreakvold volume manager vulnerabilityModerateAllowed privilege escalation via crafted messages to the volume manager. Could be exploited by malicious apps; patched in later versions.
2015Stagefright
CVE-2015-3824, CVE-2015-3864, and others
Media playback engine vulnerabilityHighAllowed remote code execution via MMS messages with crafted media files. Required no user interaction; affected millions of devices.
2016Dirty COW
CVE-2016-5195
Linux kernel race conditionModerateAllowed local privilege escalation through the copy-on-write mechanism. Required local access (e.g., an app); worked across many Android versions.
2019QualPwn
CVE-2019-10540 (with CVE-2019-10538)
Buffer overflow in Qualcomm Wi-Fi (WLAN) firmwareModerateAllowed over-the-air code execution by an attacker on the same Wi-Fi network; affected devices with many Snapdragon chipsets (e.g., Pixel 2/3).
2022CVE-2022-38181Arm Mali GPU driver vulnerabilityLow to ModerateA malicious app could gain root on phones with Mali GPUs (Pixel 6, international Samsung Galaxy S models). Arm patched it in October 2022; later listed by CISA as exploited in the wild.
2023CVE-2023-35674Android Framework privilege escalationModerateExploited in limited, targeted attacks; fixed in the September 2023 Android security update.
2024CVE-2024-32896Android Framework zero-day (privilege escalation)ModerateExploited in limited, targeted attacks; patched on Pixel phones first (June 2024), then for other Android devices.
2025CVE-2025-38352 & CVE-2025-48543Linux kernel and Android Runtime vulnerabilitiesHighEnabled privilege escalation without user interaction; confirmed active exploitation; affected unpatched devices.

Data Breaches & Security Incidents

Not every headline is a breach of Apple’s or Google’s own systems. Each entry says what was actually compromised.

Apple

2010 — iPad Email Leak (AT&T)

What happened: A flaw on AT&T’s website exposed the email addresses of over 114,000 iPad 3G owners, including government officials and celebrities.
Compromised: AT&T’s systems, not Apple’s

2012 — Mat Honan Account Takeover

What happened: Attackers social-engineered Apple support into resetting journalist Mat Honan’s iCloud account, then remotely wiped his iPhone, iPad, and Mac.
Result: Apple tightened its phone-based password-reset policy.

2014 — Celebrity iCloud Photo Leak (“Celebgate”)

What happened: Attackers used phishing and password guessing to break into celebrities’ iCloud accounts and leak private photos.
Compromised: Individual accounts (weak or phished passwords); Apple said its systems were not breached, then expanded two-factor authentication.

2016 — Apple vs. FBI (San Bernardino Case)

What happened: Apple refused an FBI demand to build software to unlock an iPhone belonging to a terrorist suspect, citing user privacy and encryption.
Note: An encryption dispute, not a breach. The FBI dropped the case after a third party unlocked the phone.

2021 — Pegasus Spyware Attack

What happened: NSO Group’s Pegasus used a zero-click iPhone vulnerability to access messages, calls, and other data.
Details: See FORCEDENTRY above.

2022 — Apple-Commissioned Data Breach Study

What happened: A study by MIT professor Stuart Madnick, commissioned by Apple, found 2.6 billion personal records were compromised in breaches across 2021 and 2022, and used it to argue for end-to-end encryption.
Note: Industry-wide context, not an Apple breach.

2022–2023 — Multiple Zero-Day Vulnerabilities

What happened: Apple patched several zero-day vulnerabilities in iOS, macOS, and Safari, some of which were reportedly exploited in the wild.

Siri recording incidents (2019) and the 2025 $95 million Siri settlement are covered on the Apple & Google Privacy page.

Google / Android

2024 — App Usage & Location Data Leaks

What happened: Device vendors (Samsung, Nokia, Tecno, etc.) leaked sensitive app usage and location data due to poor configurations and pre-installed apps.

2025 — Google Data Breach via Salesforce

What happened: Attackers used social engineering (voice phishing) to access a Google Salesforce database of business customer contacts.
Result: The stolen data fueled follow-on phishing and vishing campaigns.

Credential Leaks Affecting Both Platforms

2025 — 184 Million Record Database

What happened: An unprotected online database held 184 million plaintext logins (emails, passwords, login links) for Apple, Google, Microsoft, banking, and government accounts.
Compromised: Users’ devices (likely infostealer malware), not Apple’s or Google’s servers

2025 — 16 Billion Credential Leak

What happened: Researchers found collections totaling about 16 billion login credentials, including Apple and Google accounts, gathered mostly by infostealer malware.
Note: Much of the data is recycled from older leaks — a reminder to use unique passwords and two-factor authentication.

Sources

Note: this page cross-references the lawsuit and privacy-violation material on the Apple & Google Privacy page.
NORMAL mcbrides_resources.local
James McBride — Instructor █