[---

My Zoom API JWT leaked! What should I do?

What is a Zoom API JWT and how it is used?

The Zoom API JWT is a method of authentication that allows developers to securely access Zoom's API using JSON Web Tokens (JWT). This method ensures that only authorized users can interact with Zoom's services and protects sensitive information.

When using the Zoom API JWT, developers can utilize it for the following main use cases:

Authentication: JWT tokens can be used to authenticate and verify the identity of the application or user accessing the Zoom API.
Authorization: JWT tokens can be used to grant specific permissions and access levels to different parts of the Zoom API based on the role of the user or application.
Data Encryption: JWT tokens can be used to encrypt sensitive data transmitted between the application and the Zoom API, ensuring secure communication.

---]

[---

1. Code snippets to prevent Zoom API JWT hardcoding using environment variables

Using environment variables for storing sensitive information like Zoom API JWT in your code is a secure practice because:

Environment variables are not hardcoded in your code, reducing the risk of accidental exposure.
Environment variables can be managed separately from your codebase, making it easier to update or rotate sensitive information without changing the code.
Environment variables are not typically exposed in version control systems, providing an additional layer of security against unauthorized access.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent Zoom API JWT hardcoding using AWS Secrets Manager

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

---]

[---

3. Code snippet to prevent Zoom API JWT hardcoding using HashiCorp Vault

Using HashiCorp Vault for managing Zoom API JWTs is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a Zoom API 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 Zoom API 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 Zoom API JWT hardcoding using CyberArk Conjur

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

---]

[---

How to generate a Zoom API JWT?

To generate a Zoom API JWT, developers need to follow these steps:

Generate a base64 encoded API key and API secret.
Create a JSON payload containing the required claims such as iss (API key), exp (expiration time), and other optional claims.
Encode the JSON payload using base64url encoding.
Create a signature by concatenating the base64 encoded header, payload, and API secret, and then hash the result using HMAC SHA256.
Encode the signature using base64url encoding.
Combine the base64 encoded header, payload, and signature with dots to form the JWT.

---]

[---

My Zoom API JWT leaked, what are the possible reasons?

There are several reasons why a Zoom API JWT might have been leaked:

Improper storage: If the JWT was stored in a publicly accessible location or in a repository with weak access controls, it could have been easily accessed by unauthorized parties.
Accidental exposure: Developers may have inadvertently included the JWT in code snippets, configuration files, or logs that were shared publicly or with unauthorized individuals.
Phishing attacks: If a developer fell victim to a phishing attack and unknowingly shared their credentials, including the JWT, with malicious actors, it could have led to a leak.
Compromised systems: If the system where the JWT was stored or used was compromised due to vulnerabilities or security breaches, attackers could have gained access to the JWT.

What are the risks of leaking a Zoom API JWT

Leaking a Zoom API JWT token can pose significant risks to the security of your application and the data it handles. It's essential for developers to understand the potential consequences of such a breach in order to prioritize the protection of sensitive information.

Unauthorized Access: If a Zoom API JWT token is leaked, malicious actors could potentially gain unauthorized access to your Zoom account and all associated data.
Data Breach: The exposure of a Zoom API JWT token could lead to a data breach, compromising the confidentiality and integrity of user information.
Misuse of Resources: Attackers may misuse the leaked token to make unauthorized API calls, leading to excessive resource consumption and potential service disruptions.
Reputation Damage: A security incident resulting from a leaked Zoom API JWT token can damage the reputation of your organization and erode user trust.

---]

[---

Zoom API JWT security best practices

Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
Secure storage: store the Zoom API 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 Zoom API JWT usage and improve the overall security of your Zoom API JWT implementations.

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

---]

[---

Zoom API 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 Zoom API JWT was used by malicious actors

Review Access Logs: Check the access logs of your Zoom API 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 Zoom API JWT. This can give insights into any unauthorized use of your key.

---]

[---

Steps to revoke the Zoom API JWT

Generate a new Zoom API JWT:

Log into your Zoom API 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 Zoom API 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 Zoom API 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.

---]

payment_intent

nullable object

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

Hide

Show

child attributes

CLIENT LIBRARIES

$ gem install stripe

STRIPE-RUBY

$ pip install stripe

STRIPE-PYTHON

$ composer require stripe/stripe-php

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"

STRIPE-NODE

$ npm install --save stripe

STRIPE-NODE

$ go get github.com/stripe/stripe-go/v76

STRIPE-NODE

$ nuget install Stripe.net

STRIPE-NODE

SHOW

This is placeholder code

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents