⚠️ CVE-2025-25427: A Stored cross-site scripting ... ⚠️ CVE-2025-3509: A Remote Code Execution (RCE) ... ⚠️ CVE-2025-3246: An improper neutralization of ... 🟡 CVE-2025-3124: A missing authorization vulner... 🟢 CVE-2024-42178: HCL MyXalytics is affected by ... 🟡 CVE-2025-3765: A vulnerability, which was cla... 🟡 CVE-2025-3764: A vulnerability classified as ... 🟢 CVE-2024-42177: HCL MyXalytics is affected by ... 🟡 CVE-2025-3763: A vulnerability classified as ... 🟡 CVE-2025-3762: A vulnerability was found in P... 🟡 CVE-2025-29722: A CSRF vulnerability in Commer... 🟡 CVE-2025-28101: An arbitrary file deletion vul... 🔥 CVE-2025-28009: A SQL Injection vulnerability ... 🟢 CVE-2025-26269: DragonflyDB Dragonfly through ... 🟢 CVE-2025-26268: DragonflyDB Dragonfly before 1... ⚠️ CVE-2024-55211: An issue in Think Router Tk-Rt... 🟢 CVE-2021-47671: In the Linux kernel, the follo... ⚠️ CVE-2021-47670: In the Linux kernel, the follo... ⚠️ CVE-2021-47669: In the Linux kernel, the follo... ⚠️ CVE-2021-47668: In the Linux kernel, the follo... 🟢 CVE-2025-32415: In libxml2 before 2.13.8 and 2... ⚠️ CVE-2025-2947: IBM i 7.6  contains a privile... ⚠️ CVE-2025-29661: Litepubl CMS <= 7.0.9 is vulne... ⚠️ CVE-2025-29181: FOXCMS <= V1.25 is vulnerable ... ⚠️ CVE-2025-29180: In FOXCMS <=1.25, the installd... ⚠️ CVE-2025-29039: An issue in dlink DIR 832x 240... ⚠️ CVE-2025-43015: In JetBrains RubyMine before 2... 🟡 CVE-2025-43014: In JetBrains Toolbox App befor... 🟡 CVE-2025-43013: In JetBrains Toolbox App befor... ⚠️ CVE-2025-43012: In JetBrains Toolbox App befor... 🟡 CVE-2025-42921: In JetBrains Toolbox App befor... 🔥 CVE-2025-39596: Weak Authentication vulnerabil... 🔥 CVE-2025-39595: Improper Neutralization of Spe... ⚠️ CVE-2025-39594: Improper Neutralization of Inp... 🔥 CVE-2025-39588: Deserialization of Untrusted D... 🔥 CVE-2025-39587: Improper Neutralization of Spe... ⚠️ CVE-2025-39586: Improper Neutralization of Spe... ⚠️ CVE-2025-39583: Missing Authorization vulnerab... 🟡 CVE-2025-39580: Missing Authorization vulnerab... ⚠️ CVE-2025-39569: Improper Neutralization of Spe... ⚠️ CVE-2025-39568: Improper Limitation of a Pathn... ⚠️ CVE-2025-39567: Improper Neutralization of Inp... 🟡 CVE-2025-39562: Improper Neutralization of Inp... 🟡 CVE-2025-39559: Missing Authorization vulnerab... ⚠️ CVE-2025-39558: Improper Neutralization of Inp... 🟡 CVE-2025-39554: Missing Authorization vulnerab... 🔥 CVE-2025-39551: Deserialization of Untrusted D... 🔥 CVE-2025-39550: Deserialization of Untrusted D... ⚠️ CVE-2025-39542: Incorrect Privilege Assignment... ⚠️ CVE-2025-39535: Authentication Bypass Using an... ⚠️ CVE-2025-39533: Missing Authorization vulnerab... ⚠️ CVE-2025-39532: Missing Authorization vulnerab... ⚠️ CVE-2025-39527: Deserialization of Untrusted D... ⚠️ CVE-2025-39526: Improper Control of Filename f... ⚠️ CVE-2025-39521: Improper Neutralization of Inp... ⚠️ CVE-2025-39519: Improper Neutralization of Inp... ⚠️ CVE-2025-39464: Improper Neutralization of Inp... ⚠️ CVE-2025-39462: Improper Control of Filename f... ⚠️ CVE-2025-39461: Improper Control of Filename f... 🟡 CVE-2025-39457: Missing Authorization vulnerab... 🟡 CVE-2025-39456: Missing Authorization vulnerab... ⚠️ CVE-2025-39455: Cross-Site Request Forgery (CS... 🟡 CVE-2025-39453: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39452: Improper Control of Filename f... 🟡 CVE-2025-39444: Improper Neutralization of Inp... 🟡 CVE-2025-39443: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39442: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39441: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39440: Cross-Site Request Forgery (CS... 🟡 CVE-2025-39439: Exposure of Sensitive System I... 🟡 CVE-2025-39438: Cross-Site Request Forgery (CS... 🟡 CVE-2025-39437: Cross-Site Request Forgery (CS... 🔥 CVE-2025-39436: Unrestricted Upload of File wi... ⚠️ CVE-2025-39435: Cross-Site Request Forgery (CS... 🟡 CVE-2025-39434: Authorization Bypass Through U... ⚠️ CVE-2025-39433: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39432: Improper Neutralization of Inp... ⚠️ CVE-2025-39431: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39430: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39429: Improper Control of Filename f... 🟡 CVE-2025-39428: Improper Neutralization of Inp... 🟡 CVE-2025-39427: Improper Neutralization of Inp... 🟡 CVE-2025-39426: Cross-Site Request Forgery (CS... 🟡 CVE-2025-39425: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39424: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39423: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39422: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39421: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39420: Improper Neutralization of Inp... ⚠️ CVE-2025-39419: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39418: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39417: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39416: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39415: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-39414: Cross-Site Request Forgery (CS... ⚠️ CVE-2025-32686: Deserialization of Untrusted D... 🔥 CVE-2025-32682: Unrestricted Upload of File wi... ⚠️ CVE-2025-32674: Improper Neutralization of Inp... ⚠️ CVE-2025-32670: Improper Neutralization of Inp... ⚠️ CVE-2025-32666: Improper Neutralization of Inp...
Gravy Analytics Data Breach Exposes Unwitting Location Tracking via Popular Apps

Gravy Analytics Data Breach Exposes Unwitting Location Tracking via Popular Apps

In early January 2025, a significant data breach at Gravy Analytics, a prominent location data broker, unveiled the covert collection of user location information through numerous popular mobile applications. This revelation has intensified concerns about user privacy and the opaque operations of data brokers.

The Breach and Its Implications

Hackers infiltrated Gravy Analytics' systems, leaking approximately 1.4 gigabytes of data. This dataset included tens of millions of mobile phone coordinates from devices across the United States, Russia, and Europe, along with the names of thousands of mobile applications. Notably, the affected apps span various categories, including games like Candy Crush, dating platforms such as Tinder and Grindr, fitness trackers like MyFitnessPal, and religious apps like Muslim Pro.

Alarmingly, this data collection occurred without the explicit consent or knowledge of app developers and users. Instead of embedding specific code within the apps, Gravy Analytics exploited the real-time bidding (RTB) process in online advertising. During RTB, advertisers bid to display ads to users, inadvertently transmitting user data, including precise location information. Data brokers can intercept this data stream, enabling them to monitor user locations surreptitiously.

Privacy Concerns and Regulatory Scrutiny

The unauthorized collection and sale of sensitive location data pose significant privacy risks. Users' visits to healthcare facilities, places of worship, and participation in political activities can be tracked, potentially leading to discrimination, surveillance, and other harms. The Federal Trade Commission (FTC) has previously taken action against such practices. In December 2024, the FTC prohibited Gravy Analytics and its subsidiary, Venntel, from selling, disclosing, or using sensitive location data, mandating the deletion of previously collected data and the establishment of a sensitive data location program.

Industry Response and User Awareness

Many app developers and companies implicated in the data collection have denied any association with Gravy Analytics. For instance, Muslim Pro stated they were unaware of Gravy Analytics and did not authorize ad networks to collect user location data. Similarly, Grindr asserted that they have not shared geolocation data with ad partners for many years and do not work with data aggregators or brokers.

This incident underscores the complexities of the digital advertising ecosystem, where user data can be harvested without direct consent. It highlights the need for increased transparency and stricter regulations to protect user privacy. Users are advised to review app permissions, utilize privacy-focused tools, and stay informed about how their data is collected and used.

Conclusion

The Gravy Analytics data breach serves as a stark reminder of the vulnerabilities inherent in the digital landscape. As data brokers continue to find innovative ways to collect and monetize user information, it is imperative for regulatory bodies, app developers, and users to collaborate in safeguarding personal data and upholding privacy rights.

Sources

Back to Posts