CVE Tools

CVE-2016-1819

Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Apple Iphone OsAffected: < 9.3.2Upgrade to: 9.3.2Stated by: NVD
  • Apple TvosAffected: < 9.2.1Upgrade to: 9.2.1Stated by: NVD
  • Apple Mac Os XAffected: < 10.11.5Upgrade to: 10.11.5Stated by: NVD
  • Apple WatchosAffected: < 2.2.1Upgrade to: 2.2.1Stated by: NVD
  • Apple Inc. OS XAffected: до 10.11.5Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which Apple operating system versions your business devices are running (iOS, macOS/OS X, tvOS, watchOS).
  2. If any devices are on iOS earlier than 9.3.2, upgrade iOS to 9.3.2 or newer.
  3. If any devices are on macOS/OS X earlier than 10.11.5, upgrade OS X to 10.11.5 or newer.
  4. If any devices are on tvOS earlier than 9.2.1, upgrade tvOS to 9.2.1 or newer.
  5. If any devices are on watchOS earlier than 2.2.1, upgrade watchOS to 2.2.1 or newer.

What it is

From the CVE record

Use-after-free vulnerability in the IOAccelContext2::clientMemoryForType method in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app, a different vulnerability than CVE-2016-1817 and CVE-2016-1818.

In plain language

Written by AI from the record

This Apple iOS/macOS/tvOS/watchOS bug can let a crafted app crash the device and, in some cases, run code with high privileges; if you’re still on very old OS versions, you should act.

CVE-2016-1819 is a use-after-free issue in Apple’s IOAccelContext2::clientMemoryForType (Apple graphics/memory handling), where a crafted app can trigger memory corruption that may lead to denial of service or arbitrary code execution in a privileged context on older iOS/tvOS/macOS/watchOS releases.

If you're affected

  • Device crashes and outages
  • High-privilege code execution
  • Data exposure from compromised device
  • Disruption to mobile workflows

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS92nd
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

3 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

4.8% chance of exploitation activity in the next 30 days, which ranks it in the 92nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 61 days before the patch.

  1. EPSS band changemoderate → 0epss band change
  2. EPSS band change0 → moderateepss band change
  3. EPSS band changemoderate → 0epss band change
  4. EPSS band change0 → moderateepss band change
  5. EPSS band changemoderate → 0epss band change
  6. EPSS band changelow → moderate

Affected products

Technical detail

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for IOS, not every advisory. This one: public exploit.