Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential fix for code scanning alert no. 3: Clear-text logging of sensitive information #67

Merged
merged 1 commit into from
Mar 12, 2025

Conversation

krishnprakash
Copy link
Owner

Potential fix for https://github.com/krishnprakash/cloudflare-docs/security/code-scanning/3

To fix the problem, we need to ensure that sensitive information such as client_secret is not logged in clear text. Instead, we can log a message indicating that a service token was created without including the sensitive details. This way, we maintain the functionality of informing the user that a token was created while protecting sensitive information.

We will modify the code on line 159 to remove the logging of client_secret and replace it with a more generic message. Additionally, we will ensure that client_id is not logged if it is considered sensitive.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…nsitive information

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
@krishnprakash krishnprakash marked this pull request as ready for review March 12, 2025 16:39
@krishnprakash krishnprakash merged commit 1c4e0ac into production Mar 12, 2025
10 checks passed
@krishnprakash krishnprakash deleted the alert-autofix-3 branch March 12, 2025 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant