dbcve.org
Iphone OsOperating system · Apple

CVE-2018-4332

CRITICAL · 9.8 CVSS v3.0 Published 2019-04-03
Fix available
A fix is available. Upgrade to 5.0 / 10.14 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 memory corruption issue was addressed with improved memory handling. This issue affected versions prior to iOS 12, macOS Mojave 10.14, tvOS 12, watchOS 5.

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

Memory corruption vulnerability in Apple iOS, macOS, tvOS, and watchOS that could allow arbitrary code execution, addressed with improved memory handling in versions iOS 12, macOS Mojave 10.14, tvOS 12, and watchOS 5.

MitigationUpgrade affected Apple devices to iOS 12 or later, macOS Mojave 10.14 or later, tvOS 12 or later, or watchOS 5 or later to remediate this memory corruption vulnerability.

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
Iphone OsOperating system
Affected:< 12.0
Mac Os XOperating system
Affected:< 10.14
TvosOperating system
Affected:< 12
WatchosOperating system
Affected:< 5.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 your Apple device type
    Determine whether the device is an iPhone, iPad (iOS), Mac computer (macOS), Apple TV (tvOS), or Apple Watch (watchOS). This is needed because the version check method differs by platform.
    Affected if Device runs any of the four affected operating systems (iOS, macOS, tvOS, watchOS)
  2. Check iOS version on iPhone or iPad
    Open Settings > General > About and look at the 'Version' field. It will display a number like 11.x.x. Note that iOS 12 and later are not affected.
    Affected if Version displays less than 12.0 (for example, 11.4.1)
  3. Check macOS version on Mac
    Click the Apple menu > About This Mac. The version number appears below the macOS name (for example, 10.13.6). Compare this to 10.14.
    Affected if Version displays less than 10.14 (for example, 10.13.6 or 10.12.x)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version. The installed tvOS version is shown (for example, 11.4). Compare to version 12.
    Affected if Version displays less than 12 (for example, 11.4 or earlier)
  5. Check watchOS version on Apple Watch
    On the watch: open Settings > General > About > Version. Or on paired iPhone, open Watch app > General > About and find the watch. The version shows as 4.x.x. Compare to 5.0.
    Affected if Version displays less than 5.0 (for example, 4.3.1)

If the installed OS version is below 12.0 for iOS, 10.14 for macOS, 12 for tvOS, or 5.0 for watchOS, the device is vulnerable to this memory corruption flaw.

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 5.0 / 10.14 / 12 or later
Fixed in 5.010.1412
Interim mitigation

Upgrade affected Apple devices to iOS 12 or later, macOS Mojave 10.14 or later, tvOS 12 or later, or watchOS 5 or later to remediate this memory corruption vulnerability.

Recommended fix High confidence

iOS 12.0+, macOS Mojave 10.14+, tvOS 12+, watchOS 5.0+

  1. For iPhone/iPad: Upgrade to iOS 12.0 or later via Settings > General > Software Update
  2. For Mac: Upgrade to macOS Mojave 10.14 or later via System Preferences > Software Update
  3. For Apple TV: Upgrade to tvOS 12 or later via Settings > System > Software Updates
  4. For Apple Watch: Upgrade to watchOS 5.0 or later via the Watch app on iPhone > General > Software Update
  5. After upgrading, verify the version by checking Settings > General > About (iOS) or System Profiler (macOS)
Caveat Major OS upgrades may introduce compatibility issues with older apps or require significant user workflow adjustments; review Apple's release notes before upgrading

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

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-4332 — 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-2018-4332 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