dbcve.org
NikeApplication

CVE-2021-20834

MEDIUM · 6.1 CVSS v3.1 Published 2021-10-13
Fix available
A fix is available. Upgrade to 2.177.1 / 2.177.3.3688 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
Improper authorization in handler for custom URL scheme vulnerability in Nike App for Android versions prior to 2.177 and Nike App for iOS versions prior to 2.177.1 allows a remote attacker to lead a user to access an arbitrary website via the vulnerable App.

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

The Nike mobile applications for Android and iOS contain an improper authorization vulnerability in their custom URL scheme handler. This allows a remote attacker to craft malicious links that, when clicked, cause the app to redirect users to arbitrary websites rather than properly validating and restricting the target URLs.

MitigationUpdate the Nike App to version 2.177 or later for Android, and version 2.177.1 or later for iOS. For custom apps with similar URL scheme handling, implement strict allowlist validation for all URL scheme targets and verify the destination URL originates from trusted sources.

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
NikeApplication
Affected:< 2.177.1< 2.177.3.3688

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.1/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. Check installed Nike app version on Android
    Go to Settings > Apps > Nike, or open Google Play Store and search for the Nike app to view the installed version number
    Affected if The installed version is below 2.177.1 (Android)
  2. Check installed Nike app version on iOS
    Open the App Store, search for Nike, tap the app, and view the version information under the app description
    Affected if The installed version is below 2.177.1 (iOS) or below 2.177.3.3688 for the specific build
  3. Identify if URL scheme handling is enabled
    On Android, check app settings for deep link or URL scheme permissions under App Info > Permissions. On iOS, check Settings > Nike > URLs or verify if the app has registered custom URL schemes in the app's Info.plist
    Affected if Custom URL scheme handling is enabled and the app version is in the affected range
  4. Verify any custom URL scheme configurations
    For Android, decompile the APK and examine AndroidManifest.xml for intent-filter entries with custom schemes (e.g., nike://). For iOS, inspect the app's Info.plist for CFBundleURLTypes entries
    Affected if The app registers custom URL scheme handlers and the version is vulnerable

A user is affected if they have a Nike app version below 2.177.1 (Android) or below 2.177.1/2.177.3.3688 (iOS) with custom URL scheme handling enabled.

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 2.177.1 / 2.177.3.3688 or later
Fixed in 2.177.12.177.3.3688
Interim mitigation

Update the Nike App to version 2.177 or later for Android, and version 2.177.1 or later for iOS. For custom apps with similar URL scheme handling, implement strict allowlist validation for all URL scheme targets and verify the destination URL originates from trusted sources.

Recommended fix High confidence

Nike App for Android version 2.177+ and Nike App for iOS version 2.177.1+

  1. Open the Google Play Store (Android) or App Store (iOS) on your device
  2. Search for 'Nike' or locate the Nike App in your installed apps
  3. Update the Nike App to the latest available version
  4. For Android: Ensure the version is 2.177 or higher
  5. For iOS: Ensure the version is 2.177.1 or higher
  6. Restart the app after updating to ensure the fix takes effect

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

Fix this in Nike Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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