CVE-2019-8791
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 · uneditedAn issue existed in the parsing of URL schemes. This issue was addressed with improved URL validation. This issue is fixed in Shazam Android App Version 9.25.0, Shazam iOS App Version 12.11.0. Processing a maliciously crafted URL may lead to an open 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 · moderate confidenceThe Shazam mobile applications (Android 9.25.0 and iOS 12.11.0 and prior) contained an open redirect vulnerability due to improper validation of URL schemes during parsing. Processing a maliciously crafted URL could cause the app to redirect users to an attacker-controlled website, potentially facilitating phishing attacks or session hijacking.
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< 9.25.0< 12.11.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Shazam is installed on AndroidRun 'adb shell pm list packages | grep shazam' or check in Settings > Apps for package named 'com.shazam.andoid' or similarAffected if Shazam package is found on the device
-
Check installed Android versionRun 'adb shell dumpsys package com.shazam.android | grep versionName' or view in Settings > Apps > Shazam > VersionAffected if Version number is less than 9.25.0
-
Check if Shazam is installed on iOSCheck in Settings > General > iPhone Storage > Shazam or view in App LibraryAffected if Shazam app is listed on the iOS device
-
Check installed iOS versionOpen App Store > Shazam > Version or check in Settings > Shazam > VersionAffected if Version number is less than 12.11.0
-
Verify URL handling is activeThe app processes URLs through deep links as a core feature - this is enabled by default when the app is installed and handles shazam:// URLsAffected if Shazam is installed and can handle incoming URL schemes (shazam://)
If Shazam is installed and the version is below 9.25.0 on Android or below 12.11.0 on iOS, the environment is affected by this open redirect vulnerability.
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 data9.25.012.11.0
Update Shazam to version 9.25.0 (Android) or 12.11.0 (iOS) or later. For other applications, implement strict allowlist-based URL validation and verify that only expected, safe URL schemes are processed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8791 — 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-8791 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