dbcve.org
SafariWeb browser · Apple

CVE-2019-7292

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 5.2 / 7.11 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 validation issue was addressed with improved logic. This issue is fixed in iOS 12.2, tvOS 12.2, watchOS 5.2, Safari 12.1, iTunes 12.9.4 for Windows, iCloud for Windows 7.11. Processing maliciously crafted web content may result in the disclosure of process memory.

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

This is a memory disclosure vulnerability in WebKit (the rendering engine used by Safari, iOS, tvOS, watchOS, iTunes, and iCloud for Windows). Processing maliciously crafted web content can leak process memory due to a validation issue.

MitigationUpdate affected Apple products to the patched versions: iOS 12.2+, tvOS 12.2+, watchOS 5.2+, Safari 12.1+, iTunes 12.9.4 for Windows, or iCloud for Windows 7.11+.

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
SafariWeb browser
Affected:< 12.1
IcloudApplication
Affected:< 7.11
ItunesApplication
Affected:< 12.9.4
Iphone OsOperating system
Affected:< 12.2
TvosOperating system
Affected:< 12.2
WatchosOperating system
Affected:< 5.2

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

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

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 installed Apple products
    Check the system for Safari, iTunes, iCloud, or Apple device firmware versions. On macOS/iOS/tvOS/watchOS devices, check the installed application versions in their respective app stores or system settings. On Windows, check installed iTunes or iCloud versions in Programs and Features.
    Affected if Any of the following products are installed: Safari, iTunes, iCloud for Windows, or the device runs iOS, tvOS, or watchOS.
  2. Check Safari version
    On macOS, click Safari > About Safari to view the version number. Compare against the affected range: versions before 12.1.
    Affected if Safari version is lower than 12.1.
  3. Check iTunes version for Windows
    Open iTunes, then click Help > About iTunes to see the version. Alternatively, right-click iTunes in Programs and Features to view version. Compare against the affected range: versions before 12.9.4.
    Affected if iTunes version is lower than 12.9.4.
  4. Check iCloud for Windows version
    Open iCloud, click the gear icon or menu, and select About iCloud. Compare against the affected range: versions before 7.11.
    Affected if iCloud for Windows version is lower than 7.11.
  5. Check iOS, tvOS, or watchOS firmware version
    On the iOS device, go to Settings > General > About to view the iOS version. On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About. Compare each against the affected ranges: iOS < 12.2, tvOS < 12.2, watchOS < 5.2.
    Affected if The device firmware version is lower than 12.2 for iOS/tvOS, or lower than 5.2 for watchOS.

The environment is affected if any Safari, iTunes, iCloud for Windows, iOS, tvOS, or watchOS installation has a version below the patched thresholds (12.1, 12.9.4, 7.11, 12.2, or 5.2 respectively).

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.

From vendor data
Upgrade available Upgrade to 5.2 / 7.11 / 12.1 or later
Fixed in 5.27.1112.1
Interim mitigation

Update affected Apple products to the patched versions: iOS 12.2+, tvOS 12.2+, watchOS 5.2+, Safari 12.1+, iTunes 12.9.4 for Windows, or iCloud for Windows 7.11+.

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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