dbcve.org
IpadosOperating system · Apple

CVE-2019-8779

CRITICAL · 10.0 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 13.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A logic issue applied the incorrect restrictions. This issue was addressed by updating the logic to apply the correct restrictions. This issue is fixed in iOS 13.1.1 and iPadOS 13.1.1. Third party app extensions may not receive the correct sandbox restrictions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In iOS and iPadOS 13.x prior to 13.1.1, a logic error caused third-party app extensions to not receive correct sandbox restrictions. This could allow extensions to perform actions outside their intended security boundaries, potentially enabling privilege escalation or unauthorized data access.

MitigationApply iOS 13.1.1 or iPadOS 13.1.1 (or later) to all affected devices. For enterprises, ensure patch management processes include mobile device OS updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpadosOperating system
Affected:< 13.1.1
Iphone OsOperating system
Affected:< 13.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device OS type
    Check if the device is running iOS or iPadOS by going to Settings > General > About and looking at the model name or checking the device type
    Affected if Device is not an iPhone or iPad (the vulnerability only affects iOS and iPadOS)
  2. Determine the installed iOS/iPadOS version
    Go to Settings > General > About and read the Version field (e.g., 13.0, 13.1, 13.1.2)
    Affected if Version starts with 13. and the minor version is less than 1.1 (e.g., 13.0, 13.0.1, 13.1.0) or the version shows 13.1 without the build of 13.1.1 or later
  3. Check for installed third-party app extensions
    Go to Settings > General > Device Management (or Profiles & Device Management on some versions) to see if any third-party app extensions are installed
    Affected if Third-party extensions are installed - these are the specific targets of this sandbox bypass vulnerability
  4. Verify the patch status
    Compare your identified version against the affected range: any iOS/iPadOS version below 13.1.1 is affected
    Affected if The device is running iOS or iPadOS version 13.0 through 13.1.0 (inclusive) and has third-party extensions installed

You are affected if you are running iOS or iPadOS version 13.0 through 13.1.0 on a device that has third-party app extensions installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.1.1 or later
Fixed in 13.1.1
Interim mitigation

Apply iOS 13.1.1 or iPadOS 13.1.1 (or later) to all affected devices. For enterprises, ensure patch management processes include mobile device OS updates.

Recommended fix High confidence

iOS 13.1.1 and iPadOS 13.1.1

  1. Back up your iPhone or iPad data using iCloud or iTunes/Finder before upgrading
  2. Check your current iOS version by going to Settings > General > About
  3. To upgrade: Connect your device to power and Wi-Fi, then go to Settings > General > Software Update and download and install iOS 13.1.1 (or iPadOS 13.1.1 for iPad)
  4. Alternatively, upgrade via iTunes (Windows or older macOS) or Finder (macOS Catalina+) by connecting your device and selecting the update option
  5. After upgrade, verify the version in Settings > General > About shows 13.1.1 or later
Caveat Standard iOS upgrade considerations apply - ensure backup before upgrading; some apps may not support older iOS versions after future updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8779 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8779 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data