CodeSecDays 2024 - Join GitGuardian for a full-day exploration of cutting-edge DevSecOps solutions!

Save my spot!

CodeSecDays 2024 - Join GitGuardian for a full-day exploration of cutting-edge DevSecOps solutions!

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

[---

My Mailjet Key leaked! What should I do?

What is a Mailjet Key and how it is used?

A Mailjet Key is a unique identifier or token used to authenticate and authorize access to the Mailjet email delivery service, allowing users to securely send and manage email campaigns.

When it comes to the Mailjet Key, developers should be aware of the following main use cases:

  • Securely authenticate and authorize applications to send emails through the Mailjet API.
  • Encrypt and decrypt sensitive information, such as email content and API credentials, to ensure data privacy and protection.
  • Monitor and track email delivery metrics and performance using the Mailjet Key for analytics and reporting purposes.

---]

[---

1. Code snippets to prevent Mailjet Key hardcoding using environment variables

Using environment variables for storing sensitive information like Mailjet Keys is a good security practice because:

  • Environment variables are not hard-coded in the code, making it less likely for the keys to be exposed accidentally.
  • Environment variables are stored outside of the codebase, reducing the risk of unauthorized access to the keys.
  • Environment variables can be easily managed and updated without having to modify the code, enhancing security and scalability.
  • Environment variables are not shared publicly when code is pushed to version control systems, minimizing the chances of the keys being leaked.

How to secure your secrets using environment variables

--

---]

[---

2. Code snippet to prevent Mailjet Key hardcoding using AWS Secrets Manager

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

--

---]

[---

3. Code snippet to prevent Mailjet Key hardcoding using HashiCorp Vault

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

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

--

---]

[---

How to generate a Mailjet Key?

To generate a Mailjet API key, follow these steps:

  1. Log in to your Mailjet account.
  2. Go to the "Account Settings" section.
  3. Click on "REST API" in the sidebar.
  4. Under the "API Key Management" tab, click on "Create new API Key."
  5. Give your API key a name and select the permissions you want to grant.
  6. Click on "Create API Key" to generate the key.

For more information and detailed instructions, you can refer to the official Mailjet documentation on creating API keys here.

---]

[---

My Mailjet Key leaked, what are the possible reasons?

There are several reasons why a Mailjet Key might have been leaked:

  • Improper storage: If the key was stored in a plaintext file or hardcoded in the code without encryption, it could have been easily accessed.
  • Weak access controls: If the key was shared with individuals who did not have a need to know or if the key was not properly protected with strong access controls, it could have been leaked.
  • Phishing attacks: If a developer fell victim to a phishing attack and unknowingly shared the key with a malicious actor, it could have been leaked.
  • Insufficient monitoring: If there were no systems in place to monitor and detect unauthorized access to the key, it could have been leaked without detection.

What are the risks of leaking a Mailjet Key

When it comes to secret management, it is crucial for developers to understand the risks associated with leaking a Mailjet Key. Specifically, in the case of a Mailjet Key, the consequences of a leak can be severe due to the sensitive nature of the information it provides access to. Here are some risks developers need to be aware of:

  • Data Breaches: A leaked Mailjet Key can lead to unauthorized access to sensitive data, potentially resulting in a data breach.
  • Financial Loss: If a malicious actor gains access to your Mailjet account using the leaked key, they could send out unauthorized emails, leading to financial loss and damage to your reputation.
  • Reputation Damage: A breach of sensitive information can harm your organization's reputation and erode trust with customers and partners.
  • Legal Consequences: Depending on the nature of the data exposed, there could be legal ramifications for non-compliance with data protection regulations.

It is essential for developers to implement robust security measures to protect Mailjet Keys and other sensitive information to prevent these risks from materializing.

---]

[---

Mailjet Key security best practices

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

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

---]

[---

Mailjet Key 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 Mailjet Key was used by malicious actors

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

---]

[---

Steps to revoke the Mailjet Key

Generate a new Mailjet Key:

  • Log into your Mailjet Key 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 Mailjet Key:

  • 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 Mailjet Key.
  • 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