In most cases, trust boundaries are violated when a secret is exposed in a source code repository or an uncontrolled deployment environment.
Unintended people who don’t need to know the secret might get access to it. They might then be able to use it to gain unwanted access to associated
services or resources.
The trust issue can be more or less severe depending on the people’s role and entitlement.
What is the potential impact?
API tokens get access to the Fastly API. Tokens can be granted restricted permissions that limit access to Fastly services and resources, such
as
- Load Balancers
- Web Application Firewalls (WAF)
- TLS configuration
- Access Control Lists (ACL)
- etc.
Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the secret.
Compromise of sensitive data
If the affected service is used to store or process personally identifiable information or other sensitive data, attackers knowing an
authentication secret could be able to access it. Depending on the type of data that is compromised, it could lead to privacy violations, identity
theft, financial loss, or other negative outcomes.
In most cases, a company suffering a sensitive data compromise will face a reputational loss when the security issue is publicly disclosed.
Exceeding rate limits
Using a leaked secret, an attacker may be able to make hundreds or thousands of authenticated calls to an online service. It is common for online
services to enforce a rate limit to prevent their servers from being overwhelmed.
If an attacker is able to exceed a user-based rate limit, they may be able to cause a denial of service for the user. If this continues over a long
period of time, the user may also be subject to additional fees or may have their account terminated.
Infrastructure takeover
By obtaining a leaked secret, an attacker can gain control over your organization’s network infrastructure. They can modify DNS settings, redirect
traffic, or launch malicious instances that can be used for various nefarious activities, including launching DDoS attacks, hosting phishing websites,
or distributing malware. Malicious instances may also be used for resource-intensive tasks such as cryptocurrency mining.
This can result in legal liability, but also increased costs, degraded performance, and potential service disruptions.
Furthermore, corporate network infrastructures are often connected to other services and to the internal networks of the organization. Because of
this, cloud infrastructure is often used by attackers as a gateway to other assets. Attackers can leverage this gateway to gain access to more
services, to compromise more business-critical data and to cause more damage to the overall infrastructure.
Malware distribution
Due to this vulnerability, malware can be stored and spread, both to users of the service and to other potential targets.
A malware depends on
the attacker’s intentions, as the following examples show:
- Cryptojacking malware, whose goal is to "mine" cryptocurrencies on the affected computers or servers.
- Spyware that spies out sensitive information from victims.
In the worst case, malware can cause the target systems to be completely compromised and allow attackers to infiltrate the systems.
