Home Cyber Security News Shazam Vulnerability Could Have Exposed User Locations

Shazam Vulnerability Could Have Exposed User Locations

by Abeerah Hashim
Shazam app vulnerability

A serious vulnerability was discovered in the Shazam app that could expose the location of Android and iOS users. Thankfully, Shazam has fixed the bug before exploitation in the wild.

Shazam Vulnerability Exposing Users’ Location

Reportedly, the British security researcher Ashley King discovered a serious security vulnerability in the Shazam app. Exploiting this bug could allow an attacker to steal users’ location data.

Describing the details in a blog post, the researcher revealed that he found two different bugs in the Shazam app. Identified as CVE-2019-8791 and CVE-2019-8792, the vulnerabilities could even turn into a zero-click vulnerability for both Android and iOS platforms. The bugs remained underrated to achieve a qualification for bounty.

Specifically, the issue existed in the way Shazam handled web links. As stated in the post,

I found that a particular exported deeplink (which was responsible for loading a website inside an webview) was not validating its parameter, allowing external resources to be in control. This webview included a few javascript interfaces that allowed content to communicate with the Android & iOS API’s making it possible to pull back device specific information and the last known precise location of the user.

To exploit the bug, an attacker merely had to send a malicious link to the target user, clicking on which would open Shazam app. As soon as Shazam app would execute the link via webview, the attacker could steal victim’s location information.

Bug Patched Already

The researcher found this vulnerability back in December 2018. However, the bug only received a patch by March 2019 as Shazam underwent an acquisition by Apple.

Moreover, it took more months for Apple to decide whether the bug report qualifies for a bounty or not. Given all this scenario, the researcher has disclosed the bug only recently. Nonetheless, Shazam users don’t have to worry about their security as the issue has since been addressed.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid