Headline
CVE-2023-36817: Leaked Stripe API Key in Public Code Repository
tktchurch/website
contains the codebase for The King’s Temple Church website. In version 0.1.0, a Stripe API key was found in the public code repository of the church’s project. This sensitive information was unintentionally committed and subsequently exposed in the codebase. If an unauthorized party gains access to this key, they could potentially carry out transactions on behalf of the organization, leading to financial losses. Additionally, they could access sensitive customer information, leading to privacy violations and potential legal implications. The affected component is the codebase of our project, specifically the file(s) where the Stripe API key is embedded. The key should have been stored securely, and not committed to the codebase. The maintainers plan to revoke the leaked Stripe API key immediately, generate a new one, and not commit the key to the codebase.
A Stripe API key was found in the public code repository of our project. This sensitive information was unintentionally committed and subsequently exposed in the codebase.
Severity and Impact
The severity of this issue is HIGH. If an unauthorized party gains access to this key, they could potentially carry out transactions on behalf of our organization, leading to financial losses. Additionally, they could access sensitive customer information, leading to privacy violations and potential legal implications.
Affected Components
The affected component is the codebase of our project, specifically the file(s) where the Stripe API key is embedded. The key should have been stored securely, and not committed to the codebase.
Mitigation and Resolution
Immediate action is required to mitigate the impact of this security issue. The following steps should be taken:
- Revoke the leaked Stripe API key immediately and generate a new one. The new key should not be committed to the codebase.
- Perform a thorough audit of our code to ensure no other sensitive information has been committed.
- Implement measures to prevent sensitive information from being committed in the future. This could include using .gitignore files, secret scanning tools, and educating contributors about the importance of not committing sensitive data.
- Inform Stripe of the incident so that they can monitor for any suspicious activity.
- If applicable, notify customers of the potential data breach in accordance with relevant data protection laws and regulations.
Additional Information
The issue was discovered on 03/07/2023 during a routine secret scanning process. The issue has been logged and will be monitored to ensure that it is properly resolved.