đź“… Webinar - Delivering Security on Your Terms: An Intro to Self-Hosted

Save my spot!

đź“… Webinar - Delivering Security on Your Terms: An Intro to Self-Hosted

Save my spot!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.

[---

My Supabase Service Role JWT leaked! What should I do?

What is a Supabase Service Role JWT and how it is used?

A Supabase Service Role JWT is a JSON Web Token that allows a service to authenticate with Supabase and access resources based on the permissions granted to the service role.

Developers use the Supabase Service Role JWT for the following main use cases:

  • Authentication: Developers can use the Supabase Service Role JWT to authenticate requests made to Supabase services, ensuring secure access to resources and data.
  • Authorization: The JWT can be used to verify the identity and permissions of the requesting entity, allowing developers to control access to specific functionalities or data within their applications.
  • Auditing and Logging: By utilizing the Supabase Service Role JWT, developers can track and log the actions performed by different service roles, enabling detailed auditing and monitoring of system activities.

---]

[---

1. Code snippets to prevent Supabase Service Role JWT hardcoding using environment variables

Using environment variables for storing Supabase Service Role JWT in your code is a secure practice for the following reasons:

  • Environment variables are not hard-coded in the codebase, reducing the risk of exposure through version control systems or code reviews.
  • Environment variables are stored outside of the application code, making it harder for attackers to access sensitive information through code analysis or exploitation.
  • Environment variables can be managed and secured at the operating system level, providing an extra layer of protection against unauthorized access.

How to secure your secrets using environment variables

--

---]

[---

2. Code snippet to prevent Supabase Service Role JWT hardcoding using AWS Secrets Manager

Using AWS Secrets Manager to manage Supabase Service Role JWTs is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Supabase Service Role JWT from AWS Secrets Manager.

--

---]

[---

3. Code snippet to prevent Supabase Service Role JWT hardcoding using HashiCorp Vault

Using HashiCorp Vault for managing Supabase Service Role JWTs is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a Supabase Service Role JWT using HashiCorp Vault.

Remember to replace the VAULT_ADDR and VAULT_TOKEN with your Vault server address and authentication token. The snippets assume that the Supabase Service Role JWT is stored under the api_key field within Vault. The specifics of the Vault path and field names should be adjusted to match your Vault setup.

--

---]

[---

4. Code snippet to prevent Supabase Service Role JWT hardcoding using CyberArk Conjur

Using CyberArk Conjur to manage Supabase Service Role JWT is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Supabase Service Role JWT from CyberArk Conjur.

--

---]

[---

How to generate a Supabase Service Role JWT?

To generate a Supabase Service Role JWT, follow these steps:

  1. Authenticate with your Supabase project using a service role secret key.
  2. Construct a JSON object containing the necessary claims for the JWT, such as the role name and any custom claims.
  3. Sign the JSON object using the service role secret key to generate the JWT.

---]

[---

My Supabase Service Role JWT leaked, what are the possible reasons?

There are several reasons why a Supabase Service Role JWT might have been leaked:

  • Weak or compromised authentication credentials used to access the JWT.
  • Vulnerabilities in the code or infrastructure where the JWT is stored.
  • Improper handling or storage of the JWT, such as hardcoding it in the code or storing it in a public repository.
  • Exposure of the JWT through insecure communication channels.
  • Insufficient access controls leading to unauthorized access to the JWT.

What are the risks of leaking a Supabase Service Role JWT

When it comes to Supabase Service Role JWT, it is crucial for developers to understand the risks associated with leaking this specific token. Here are some of the key risks:

  • Unauthorized Access: If a Supabase Service Role JWT is leaked, it can be used by malicious actors to gain unauthorized access to sensitive data and resources within your Supabase project.
  • Data Breaches: Leaking a Supabase Service Role JWT can lead to potential data breaches, as attackers can exploit the token to retrieve, modify, or delete sensitive information stored in your database.
  • Compromised Security: The leakage of a Supabase Service Role JWT can compromise the overall security of your application, putting both user data and system integrity at risk.
  • Reputation Damage: In the event of a security incident resulting from a leaked Supabase Service Role JWT, your organization's reputation may suffer, leading to loss of trust from users and stakeholders.

Therefore, it is essential for developers to follow best practices in secret management and detection to prevent the leakage of sensitive tokens like the Supabase Service Role JWT.

---]

[---

Supabase Service Role JWT security best practices

  • Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
  • Secure storage: store the Supabase Service Role JWT in a secure location, such as a password manager or a secrets management service.
  • Regular rotation: periodically rotate the API key to minimize the risk of long-term exposure.
  • Restrict permissions: apply the principle of least privilege by only granting the key the minimum necessary permissions.
  • Monitor usage: regularly check the usage logs for any unusual activity or unauthorized access attempts.
  • Implement access controls: limit the number of users who have access to the secret and enforce strong authentication measures.
  • Use a secrets manager: utilize secret management tools like CyberArk or AWS Secrets Manager for enhanced security.

By adhering to the best practices, you can significantly reduce the risk associated with Supabase Service Role JWT usage and improve the overall security of your Supabase Service Role JWT implementations.

Exposing secrets on GitHub: What to do after leaking Credential and API keys

---]

[---

Supabase Service Role JWT leak remediation: what to do

What to do if you expose a secret: How to stay calm and respond to an incident [cheat sheet included]

How to check if Supabase Service Role JWT was used by malicious actors

  • Review Access Logs: Check the access logs of your Supabase Service Role JWT account for any unauthorized access or unusual activity. Pay particular attention to access from unfamiliar IP addresses (if you haven’t set up a specific allow list) or at odd hours.
  • Monitor Usage Patterns: Look for anomalies in the usage patterns, such as unexpected spikes in data access or transfer.
  • Check Active Connections and Operations: Review the list of active connections and recent operations on your database. Unusual or unauthorized operations might indicate malicious use.
  • Audit API Usage: If possible, audit the usage of your API key through any logging or monitoring services you have integrated with Supabase Service Role JWT. This can give insights into any unauthorized use of your key.

---]

[---

Steps to revoke the Supabase Service Role JWT

Generate a new Supabase Service Role JWT:

  • Log into your Supabase Service Role JWT account.
  • Navigate to the API section and generate a new API key.

Update Services with the new key:

  • Replace the compromised key with the new key in all your services that use this API key.
  • Ensure all your applications and services are updated with the new key before deactivating the old one.

Deactivate the old Supabase Service Role JWT:

  • Once the new key is in place and everything is functioning correctly, deactivate the old API key.
  • This can typically be done from the same section where you generated the new key.

Monitor after key rotation:

  • After deactivating the old key, monitor your systems closely to ensure that all services are running smoothly and that there are no unauthorized access attempts.

---]

[---

How to understand which services will stop working

  • Inventory of services: keep an inventory of all services and applications that utilize your Supabase Service Role JWT.
  • Communication and documentation: Ensure that your team is aware of which services are dependent on the key. Maintain documentation for quick reference.
  • Testing: before deactivating the old key, test your services with the new key in a staging environment. This helps in identifying any services that might face issues post rotation.
  • Fallback strategies: Have a fallback or emergency plan in case a critical service fails after the key rotation. This might include temporary measures or quick rollback procedures.

In summary, the remediation process involves identifying potential misuse, carefully rotating the key, and ensuring minimal disruption to services. Being proactive and having a well-documented process can greatly reduce the risks associated with a compromised API key.

---]

[---

What about other secrets?

GitGuardian helps developers keep 350+ types of secrets out of source code. GitGuardian’s automated secrets detection and remediation solution secure every step of the development lifecycle, from code to cloud:

  • On developer workstations with git hooks (pre-commit and pre-push);
  • On code sharing platforms like GitHub, GitLab, and Bitbucket;
  • In CI environments (Circle CI, Travis CI, Jenkins CI, GitHub Actions, and many more);
  • In Docker images.

---]

Environment Variables
Environment Variables
Environment Variables

charge

nullable string

For card errors, the ID of the failed charge.

payment_method_type

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

doc_url

nullable string

A URL to more information about the error code reported.

request_log_url

nullable string

A URL to the request log entry in your dashboard.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

payment_intent

nullable object

The PaymentIntent object for errors returned on a request involving a PaymentIntent.

setup_intent

nullable object

The SetupIntent object for errors returned on a request involving a SetupIntent.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

CLIENT LIBRARIES

$ gem install stripe
$ pip install stripe
$ composer require stripe/stripe-php
MAVEN
<dependency>
  <groupId>com.stripe</groupId>
  <artifactId>stripe-java</artifactId>
  <version>24.16.0</version>
</dependency>

GRADLE
compile "com.stripe:stripe-java:24.16.0"
$ npm install --save stripe
$ go get github.com/stripe/stripe-go/v76
$ nuget install Stripe.net
SHOW
{{this.title}}
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
{{clipboardIconText}}
This is placeholder code