Security Experts:

Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Application Security

Leaked Algolia API Keys Exposed Data of Millions of Users

Threat detection firm CloudSEK has identified thousands of applications leaking Algolia API keys, and tens of applications with hardcoded admin secrets, which could allow attackers to steal the data of millions of users.

Threat detection firm CloudSEK has identified thousands of applications leaking Algolia API keys, and tens of applications with hardcoded admin secrets, which could allow attackers to steal the data of millions of users.

Organizations can use Algolia’s API to incorporate into their applications functions such as search, discovery, and recommendations. The API is used by over 11,000 companies, including Lacoste, Slack, Medium, and Zendesk.

CloudSEK says it has identified 1,550 applications that leaked Algolia API keys, including 32 apps that had hardcoded admin secrets, providing attackers with access to pre-defined Algolia API keys.

The offending 32 apps, CloudSEK says, had more than 2.5 million downloads, potentially exposing the data of their users to malicious attacks. A threat actor could exploit these weaknesses to read user information, including IP addresses, access details, and analytics data, and delete user information.

“While this is not a flaw in Algolia or other such services that provide integrations, it is evidence of how API keys are mishandled by app developers. So, it is up to individual companies to address the security concerns associated with payment gateways, AWS services, open firebases,” CloudSEK points out.

The Algolia API requires that the Application ID and API key are passed via two headers, to use services such as search, browse index, add records/delete records, list/update indexes, read/update index settings, and to retrieve logs and information from APIs.

An attacker with access to the leaked API keys could access any of these features and read information they should not have access to.

CloudSEK points out that organizations should revoke the leaked API keys and generate new ones that are stored securely, and that authenticated endpoints should be used to communicate with sensitive, external APIs, to prevent the leak of secrets.

The company says it has informed both Algolia and the affected organizations of the hardcoded API keys.

Related: Thousands of Secret Keys Found in Leaked Samsung Source Code

Related: Researchers Find Tens of AWS APIs Leaking Sensitive Data

Related: Twitter Says Bug Leading to API Key Leak Patched

Written By

Ionut Arghire is an international correspondent for SecurityWeek.

Click to comment

Expert Insights

Related Content

Application Security

Cycode, a startup that provides solutions for protecting software source code, emerged from stealth mode on Tuesday with $4.6 million in seed funding.

Application Security

Drupal released updates that resolve four vulnerabilities in Drupal core and three plugins.

Application Security

A CSRF vulnerability in the source control management (SCM) service Kudu could be exploited to achieve remote code execution in multiple Azure services.

Application Security

PayPal is alerting roughly 35,000 individuals that their accounts have been targeted in a credential stuffing campaign.

Application Security

Many developers and security people admit to having experienced a breach effected through compromised API credentials.

Application Security

A new report finds that barely 1% of all SBOMs being generated today meets the “minimum elements” defined by the U.S. government.

Application Security

A security vulnerability identified on AliExpress, the wholesale marketplace owned by the Chinese e-commerce giant Alibaba, could have been exploited by hackers to hijack...

Application Security

Electric car maker Tesla is using the annual Pwn2Own hacker contest to incentivize security researchers to showcase complex exploit chains that can lead to...