Russia-linked APT29 reused iOS and Chrome exploits previously developed by NSO Group and Intellexa
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2021-1879 | Universal XSS in Apple WebKit on iOS, iPadOS, and watchOS (Actively Exploited) CVE-2021-1879 is a universal cross-site scripting (UXSS) flaw in the WebKit browser engine affecting iOS, iPadOS, and watchOS, caused by an object-lifetime management error. An attacker can trigger it by convincing a user to process maliciously crafted web content (e.g., visiting an attacker-controlled page in Safari or another WebKit-based browser), allowing the attacker to bypass the same-origin policy and read or modify content of other sites in the browser. Successful exploitation is rated Medium severity (CVSS 6.1) because it requires user interaction, but it can leak sensitive data such as cookies, session tokens, or page content. Any user of an iPhone, iPad, or Apple Watch running software older than iOS 12.5.2, iOS 14.4.2/iPadOS 14.4.2, or watchOS 7.3.3 is affected. Apple reported that the issue may have been actively exploited in the wild at the time of patching, it is on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), and public reporting tied its use to targeted campaigns (including Russian SVR-linked operations), though no public proof-of-concept is known. Do: Update devices to iOS 12.5.2 (older devices) or iOS 14.4.2/iPadOS 14.4.2, and Apple Watch devices to watchOS 7.3.3, per Apple's instructions. Because exploitation requires loading malicious web content in WebKit, avoid following untrusted web links on unpatched devices until updated; verify fleet-wide OS versions and confirm the fix, since this CVE is on the CISA KEV catalog with patching required. Check logs or browser history for signs of visits to attacker-controlled sites on devices that have since been updated, as no public proof-of-concept exists to test against. | 6.1 | 7% | KEV |
| masshundreds of millions of devices (Apple's active iPhone/iPad/watchOS install base was on the order of 1+ billion when patched; all unpatched devices are exposed… | |
| CVE-2023-41993 | WebKit Code Execution Flaw in Apple iOS, iPadOS, macOS, and Safari Apple's WebKit engine, which renders web content for Safari and for essentially all HTML processing on iOS, iPadOS, and macOS, contains a flaw that leads to code execution when processing maliciously crafted web content. It is triggered when a user's browser or embedded web view loads attacker-controlled web content, so simply visiting a hostile page can be enough. Successful exploitation could allow arbitrary code execution within the affected application's context, a common stepping stone to broader device compromise. All users of Apple iOS, iPadOS, macOS, and Safari are potentially affected, as are users of non-Apple products that rely on WebKit for HTML processing. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2023-09-25, indicating confirmed in-the-wild exploitation; no public proof-of-concept is known. Do: Apply Apple's latest security updates for iOS, iPadOS, macOS, and Safari that patch WebKit, following the vendor instructions referenced by the CISA KEV entry, and treat unpatched WebKit builds as actively exploited. Until systems are patched, restrict exposure to untrusted web content (e.g., limit browsing and in-app web views to trusted sites for high-risk users). Also inventory any non-Apple applications or HTML-processing components in your environment that bundle WebKit and update them as their maintainers ship fixes. | 8.8 | 29% | KEV |
| mass1+ billion devices/users (WebKit ships in Safari and all web-content rendering on iOS, iPadOS, and macOS) | |
| CVE-2024-4671 | Use-After-Free Sandbox Escape in Google Chrome/Chromium CVE-2024-4671 is a use-after-free (CWE-416) in the Visuals component of Google Chrome and Chromium, fixed in Chrome 124.0.6367.201. It is triggered via a crafted HTML page, but the attacker must already have compromised the browser's renderer process, so this flaw is typically chained with a renderer exploit rather than used standalone. Successful exploitation enables a sandbox escape, letting the attacker break out of Chrome's renderer sandbox and gain broader access to the system beyond the browser tab. All users of Google Chrome versions prior to 124.0.6367.201 are affected, and per CISA's CPE data, Fedora's packaged Chromium builds are also in scope. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2024-05-13, indicating active exploitation in the wild; no public proof-of-concept is known, EPSS estimates an 8.3% chance of exploitation within 30 days (95th percentile), and ransomware association is unknown. Do: Update Google Chrome to 124.0.6367.201 or later (verify via chrome://settings/help, since Chrome auto-updates may lag), and update Fedora's chromium package to the fixed build; CISA KEV requires federal agencies to apply the vendor fix on the mandated timeline. Because this sandbox escape must be chained with a renderer compromise, defenders should treat any unpatched Chrome deployment as exposed and confirm via EDR logs whether suspicious renderer-process activity occurred; enterprise admins should push the update through managed-browser channels immediately. | 9.6 | 8% | KEV |
| mass≈3+ billion Chrome/Chromium users worldwide (Chrome holds roughly 65% of desktop browser market share, with additional exposure via Chromium packaged in Fedora) | |
| CVE-2024-5274 | Google Chrome V8 Type Confusion Allows In-Sandbox RCE via Crafted HTML Pages CVE-2024-5274 is a type confusion flaw (CWE-843) in the V8 JavaScript engine of Google Chrome prior to 125.0.6422.112. A remote attacker can trigger it by persuading a user to open or interact with a crafted HTML page. Successful exploitation allows the attacker to execute arbitrary code inside the browser's sandbox, and the scope-changed CVSS scoring indicates potential impact beyond the browser process itself. Anyone running an affected Chrome or Chromium build, including Chromium-derived distributions such as Fedora's Chromium package, is exposed. The flaw was added to CISA's KEV on 2024-05-28, a public PoC reference exists, and related news reports describe it as actively exploited in the wild. Do: Upgrade Google Chrome to 125.0.6422.112 or later and confirm the build via chrome://version; Fedora users and users of Chromium-derived browsers should install the corresponding updated packages from their vendor. Because the flaw is listed in CISA KEV, federal agencies and targeted organizations must apply the vendor fix or discontinue use per the required action, and all users should avoid untrusted web content until patched. | 9.6 | 7% | KEV PoC |
| masson the order of billions of users (Chrome has 3+ billion users and roughly two-thirds desktop browser share) |
Indicators of compromiseauto-extracted · verify before use · export allAll →
| Type | Indicator | Context |
|---|---|---|
| domain | ceo-adviser.com | 024, mfa.gov.mn was compromised again, this time linking to ceo-adviser.com and delivering the same exploit and payload, but updated to |
| domain | track-adv.com | mpromised a third time, redirecting Android Chrome users to track-adv.com to exploit CVE-2024-5274 and CVE-2024-4671 , deploying a Ch |
Full article812 words · extracted from securityaffairs.com · click to collapse

Russia-linked APT29 group was spotted reusing iOS and Chrome exploits previously developed by surveillance firms NSO Group and Intellexa.
Google TAG (Threat Analysis Group) researchers observed the Russia-linked group APT29 (aka SVR group, BlueBravo, Cozy Bear, Nobelium, Midnight Blizzard, and The Dukes). using exploits previously used by surveillance software vendors NSO Group and Intellexa. The circumstance suggests that the nation-state actors may have purchased the surveillance tools from the surveillance firms.
TAG experts detected multiple exploit campaigns between November 2023 and July 2024 that were used in watering hole attacks on Mongolian government websites. These campaigns targeted both iOS and Android users, exploiting iOS versions older than 16.6.1 and Android Chrome versions from m121 to m123. Despite the vulnerabilities being addressed, Google notified Apple, Android, and Chrome teams, as well as the Mongolian CERT, to address the compromised sites. The findings highlight the ongoing risk posed by watering hole attacks and the collaboration between nation-state actors and commercial surveillance vendors.
APT29 compromised the websites of the Mongolian cabinet (cabinet.gov.mn) and Ministry of Foreign Affairs (mfa.gov.mn), they embedded hidden iframes linked to attacker-controlled sites. In November 2023, these iframes led to the site track-adv.com, delivering a CVE-2023-41993 exploit targeting iPhones running iOS 16.6.1 or older, deploying a cookie-stealing payload previously associated with APT29. The researchers noticed that by February 2024, mfa.gov.mn was compromised again, this time linking to ceo-adviser.com and delivering the same exploit and payload, but updated to target specific websites like webmail.mfa.gov.mn. In July 2024, the site mfa.gov.mn was compromised a third time, redirecting Android Chrome users to track-adv.com to exploit CVE-2024-5274 and CVE-2024-4671, deploying a Chrome information-stealing payload.
Google also observed Apple Safari campaigns that were conducted between November 2023 and February 2024. Threat actors conducted a watering hole attack to deliver an iOS exploit through CVE-2023-41993. When accessed by an iPhone or iPad, the compromised sites used an iframe to deploy a reconnaissance payload that validated the device before downloading a WebKit exploit to steal browser cookies. This exploit only affected devices running iOS 16.6.1 or older, while those on iOS 16.7 or with lockdown mode enabled were protected.
“When visited with an iPhone or iPad device, the watering hole sites used an iframe to serve a reconnaissance payload, which performed validation checks before ultimately downloading and deploying another payload with the WebKit exploit to exfiltrate browser cookies from the device.” reads the TAG’s report. “The WebKit exploit did not affect users running the current iOS version at the time (iOS 16.7), working only on iOS versions 16.6.1 or older. Users with lockdown mode enabled were not affected even when running a vulnerable iOS version.”
The exploit employed in this campaign shared the exact same trigger as one previously used by Intellexa, suggesting a strong connection between the authors or providers of both exploits. However, it is unclear how the attackers obtained this exploit.
“The iOS exploit loaded the same cookie stealer framework that TAG observed in March 2021 when a Russian government-backed attacker exploited CVE-2021-1879 to acquire authentication cookies from prominent websites such as LinkedIn, Gmail and Facebook.” continues the report. “In that campaign, attackers used LinkedIn Messaging to target government officials from western European countries by sending them malicious links.”
Google TAG also shared details of a new watering hole attack that occurred in late July 2024. Threat actors compromised the mfa.gov.mn website, targeting Android users via a Google Chrome exploit chain. This attack was similar to a previous iOS exploit, both aiming to steal credential cookies using n-day vulnerabilities. However, the Chrome attack involved more technical complexity, including a sandbox escape to bypass Chrome’s site isolation. APT29 used obfuscated JavaScript to inject a malicious iframe and employed ECDH key exchange for encryption. The attack also utilized indexedDB for storing client-side status information, with unique identifiers used consistently throughout the stages.
APT29 chained two vulnerabilities in the exploit used in this attack. The first, CVE-2024-5274, was used to compromise the Chrome browser’s renderer. This vulnerability was discovered and reported as an in-the-wild 0-day in May 2024 by Google’s Threat Analysis Group (TAG) and Chrome Security, after being used by the NSO Group, a commercial surveillance vendor (CSV). Although the attackers adapted NSO Group’s exploit, their version targeted only Chrome versions 121 to 123, whereas the NSO exploit supported a broader range of versions, from 107 to 124. The experts pointed out that despite sharing a similar trigger, the two exploits are conceptually different.

“What is clear is that APT actors are using n-day exploits that were originally used as 0-days by CSVs. It should be noted that outside of common exploit usage, the recent watering hole campaigns otherwise differed in their approaches to delivery and second-stage objectives.” Google TAG concludes.
Follow me on Twitter: @securityaffairs and Facebook and Mastodon
(SecurityAffairs – hacking, APT29)
Text extracted automatically; images, tables and formatting may be missing. Original: https://securityaffairs.com/167797/apt/apt29-nso-group-and-intellexa-mobile-exploits.html