CVE-2019-7288
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 · uneditedThe issue was addressed with improved validation on the FaceTime server. This issue is fixed in macOS Mojave 10.14.3 Supplemental Update, iOS 12.1.4. A thorough security audit of the FaceTime service uncovered an issue with Live Photos .
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 vulnerability in the FaceTime service related to Live Photos functionality allowed an attacker to potentially capture Live Photos without the target user's knowledge or consent during a FaceTime call. The issue was addressed through improved validation implemented on the FaceTime server side.
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.1.4< 10.14.3CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device platformDetermine whether the device is an iPhone (iOS) or a Mac computer (macOS). This will determine which version range applies.Affected if Device runs iOS or macOS and uses FaceTime
-
Check iOS version on iPhoneOn the iPhone, go to Settings > General > About and note the version number displayed next to 'Version'.Affected if The installed iOS version is lower than 12.1.4
-
Check macOS version on MacOn the Mac, click the Apple menu > About This Mac and note the version number displayed under macOS.Affected if The installed macOS version is lower than 10.14.3
-
Confirm FaceTime usageVerify whether the FaceTime application is installed and has been used on the device. The vulnerability only affects users who use FaceTime.Affected if FaceTime has been used and the OS version is below the patched release
A user is affected if they are running iOS versions prior to 12.1.4 or macOS versions prior to 10.14.3 on a device where FaceTime is installed and has been used.
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.
dbcve · scoped10.14.312.1.4
Apply the vendor-supplied patches: macOS Mojave 10.14.3 Supplemental Update or iOS 12.1.4. This appears to be a server-side fix that does not require end-user configuration.
iOS 12.1.4 and macOS Mojave 10.14.3 Supplemental Update
- For iOS devices: Go to Settings > General > Software Update and install iOS 12.1.4
- For Mac devices: Go to System Preferences > Software Update and install the macOS Mojave 10.14.3 Supplemental Update
- After updating, verify the version by checking Settings > General > About on iOS or System Preferences > About This Mac on macOS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7288 — 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-2019-7288 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