Skip to main content

CVE-2021-30666Apple iOS WebKit Buffer Overflow Vulnerability

Patch nowHigh8.8Exploited, CISA due date 2021-11-17EPSS 3.0%, higher than 87% of scored CVEs

CVE-2021-30666 is a memory buffer error in Apple iOS, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

Code reads or writes outside the memory it was given, which can corrupt the process.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03: it is being exploited in the wild. EPSS estimates a 3.0% chance of exploitation activity in the next 30 days, higher than 87% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2021-11-17.
  2. Upgrade Apple iOS to 12.5 or later. The patch notes are linked below.
  3. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Warn the people who use it, and filter files and links on the way in.
  5. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

A buffer overflow issue was addressed with improved memory handling. This issue is fixed in iOS 12.5.3. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited..

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

  • Where does Apple iOS run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.