dbcve.org
SafariWeb browser · Apple

CVE-2017-7153

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 4.2 / 7.2 or later.
See remediation →
68/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
An issue was discovered in certain Apple products. iOS before 11.2 is affected. Safari before 11.0.2 is affected. iCloud before 7.2 on Windows is affected. iTunes before 12.7.2 on Windows is affected. tvOS before 11.2 is affected. watchOS before 4.2 is affected. The issue involves the "WebKit" component. It allows remote attackers to spoof user-interface information (about whether the entire content is derived from a valid TLS session) via a crafted web site that sends a 401 Unauthorized redirect.

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 · high confidence

This is a UI spoofing vulnerability in WebKit where a remote attacker can trick the browser into displaying secure/TLS indicators (like the padlock icon) even when content is not actually served over a valid TLS session. The attack works by using a crafted website that sends a 401 Unauthorized redirect, causing the browser to misrepresent the security status of the page content.

MitigationUpdate all affected Apple products (iOS 11.2+, Safari 11.0.2+, iCloud 7.2+, iTunes 12.7.2+, tvOS 11.2+, watchOS 4.2+) to their patched versions to resolve the WebKit UI spoofing issue.

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:< 11.0.2
Ubuntu LinuxOperating system
Affected:= 16.04= 17.10
Iphone OsOperating system
Affected:< 11.2
TvosOperating system
Affected:< 11.2
WatchosOperating system
Affected:< 4.2
IcloudApplication
Affected:< 7.2
ItunesApplication
Affected:< 12.7.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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 WebKit-based products in use
    Check installed software for Safari, iOS, tvOS, watchOS, iCloud, or iTunes. On Linux, check if WebKitGTK is installed (dpkg -l | grep webkit or rpm -qa | grep webkit)
    Affected if Any of these products are present and their version cannot be verified or is below patched versions
  2. Check Safari version
    Open Safari > About Safari or run: /Applications/Safari.app/Contents/MacOS/Safari --version
    Affected if Version is lower than 11.0.2
  3. Check iOS version
    Go to Settings > General > About on iPhone/iPad, or check device management console
    Affected if Version is lower than 11.2
  4. Check tvOS or watchOS version
    Check Settings > General > About on Apple TV or Apple Watch, or check via device management
    Affected if tvOS is lower than 11.2 or watchOS is lower than 4.2
  5. Check iCloud or iTunes version
    iCloud: Check installed version in iCloud for Windows app. iTunes: Open iTunes > Help > About iTunes, or run: /Applications/iTunes.app/Contents/MacOS/iTunes --version
    Affected if iCloud version is lower than 7.2 or iTunes version is lower than 12.7.2

You are affected if any WebKit-based product (Safari, iOS, tvOS, watchOS, iCloud, iTunes) is present and its version falls below the patched thresholds (Safari 11.0.2+, iOS 11.2+, tvOS 11.2+, watchOS 4.2+, iCloud 7.2+, iTunes 12.7.2+).

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 4.2 / 7.2 / 11.0.2 or later
Fixed in 4.27.211.0.2
Interim mitigation

Update all affected Apple products (iOS 11.2+, Safari 11.0.2+, iCloud 7.2+, iTunes 12.7.2+, tvOS 11.2+, watchOS 4.2+) to their patched versions to resolve the WebKit UI spoofing issue.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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