dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Jul 2022.
Iphone OsOperating system · Apple

CVE-2018-4344

HIGH · 7.8 CVSS v3.1 Published 2019-04-03
Fix available
A fix is available. Upgrade to 5.0 / 10.14 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild No privileges

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's iOS, macOS, tvOS, and watchOS operating systems that was addressed through improved memory handling. The specific vulnerability type and attack vector are not detailed in the available information.

MitigationApply the vendor-supplied updates: iOS 12 or later, macOS Mojave 10.14 or later, tvOS 12 or later, and watchOS 5 or later.

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.0
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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 and operating system
    Determine whether you are using an iPhone/iPad (iOS), Mac (macOS), Apple TV (tvOS), or Apple Watch (watchOS). On iOS, go to Settings > General > About. On macOS, click the Apple menu > About This Mac. On tvOS, go to Settings > General > About. On watchOS, open the Watch app on iPhone > General > About.
    Affected if The device runs any of the affected Apple operating systems and the version is below the fixed release.
  2. Check iOS version on iPhone or iPad
    Open Settings > General > About and look at the 'Version' field. Compare the numeric version (for example, 11.4.1) against 12.0.
    Affected if The iOS version starts with 11.x or any version number less than 12.0.
  3. Check macOS version on Mac
    Click the Apple menu in the top-left corner, select About This Mac, and note the version number displayed (for example, 10.13.6). Compare against 10.14.
    Affected if The macOS version is 10.13.x or any version below 10.14 (Mojave).
  4. Check tvOS version on Apple TV
    Go to Settings > General > About and read the version number. Compare against 12.0.
    Affected if The tvOS version is below 12.0.
  5. Check watchOS version on Apple Watch
    On the paired iPhone, open the Watch app, go to General > About, and read the watchOS version. Alternatively, on the Watch go to Settings > General > About. Compare against 5.0.
    Affected if The watchOS version is below 5.0.

You are affected if your device runs iOS prior to 12.0, macOS prior to 10.14, tvOS prior to 12.0, or watchOS prior to 5.0.

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.0 or later
Fixed in 5.010.1412.0
Interim mitigation

Apply the vendor-supplied updates: iOS 12 or later, macOS Mojave 10.14 or later, tvOS 12 or later, and watchOS 5 or later.

Recommended fix High confidence

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

  1. Back up all important data on the device before upgrading
  2. For iPhone/iPad/iPod: Go to Settings > General > Software Update and install iOS 12.0 or later
  3. For Mac: Go to System Preferences > Software Update and install macOS Mojave 10.14 or later
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 12.0 or later
  5. For Apple Watch: Go to Settings > General > Software Update on the iPhone paired with the watch, or Settings > General > Software Update directly on watchOS 5.0 or later
  6. After upgrading, verify the device is running the fixed version in Settings > General > About (iOS) or System Preferences > About (macOS)
Caveat Major OS upgrades may cause incompatibility with older applications or features not supported in the new version; some legacy software may no longer function

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

Fix this in Iphone Os Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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