CVE-2018-4425
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 · uneditedA 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 confidenceA memory corruption vulnerability in Apple's iOS, macOS, tvOS, and watchOS operating systems that was addressed through improved memory handling. The flaw existed in versions prior to iOS 12, macOS Mojave 10.14, tvOS 12, and watchOS 5. The high CVSS score of 7.8 indicates the vulnerability is relatively easy to exploit with potential for complete compromise, though the specific attack vector and affected component are not detailed in the available documentation.
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< 12.0< 10.14< 12.0< 5.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device typeDetermine whether the device is an iPhone, iPad (iOS), Mac computer (macOS), Apple TV (tvOS), or Apple Watch (watchOS). This determines which OS version threshold applies.Affected if Device runs any of the listed Apple operating systems and the specific OS version cannot be determined or is below the fixed versions.
-
Check iOS version on iPhone or iPadOpen Settings app, tap General, tap About, and note the Version number displayed.Affected if The reported iOS version is earlier than 12.0 (for example, 11.4.1 or 11.x).
-
Check macOS version on MacClick the Apple menu in the upper-left corner, select About This Mac, and note the version number shown under the macOS name.Affected if The reported macOS version is earlier than 10.14 (Mojave), such as 10.13.x or earlier.
-
Check tvOS version on Apple TVOpen Settings app on Apple TV, go to General, select About, and note the version number.Affected if The reported tvOS version is earlier than 12.0 (for example, 11.4.x or earlier).
-
Check watchOS version on Apple WatchOn the paired iPhone, open the Watch app, go to General, select About, and note the watchOS version. Alternatively, check on the watch via Settings > General > About.Affected if The reported watchOS version is earlier than 5.0 (for example, 4.x).
If any detected OS version falls below 12.0 (iOS/tvOS), 10.14 (macOS), or 5.0 (watchOS), the device is running a vulnerable version and is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data5.010.1412.0
Apply vendor-supplied OS updates: upgrade iOS devices to version 12 or later, macOS systems to Mojave 10.14 or later, tvOS devices to version 12 or later, and watchOS devices to version 5 or later.
- Consultation2.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,976.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-4425 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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