Skip to content

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

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

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/1

To fix the problem, we need to ensure that sensitive information such as client_secret is not logged in clear text. Instead of logging the entire command, we can log a sanitized version of it that excludes the sensitive information. This way, we can still have useful logging for debugging purposes without exposing sensitive data.

We will modify the logging statement on line 72 to exclude the client_secret from the logged command. We will also add a helper function to sanitize the command before logging it.

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 15:28
@krishnprakash krishnprakash merged commit 553d584 into production Mar 12, 2025
10 checks passed
@krishnprakash krishnprakash deleted the alert-autofix-1 branch March 12, 2025 15:28
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