fix: sensitive data exposure in console logs #7975
Closed
+621
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ticket:WP-7503 Prevent sensitive data exposure in console logs Implements automatic sanitization of console output to prevent sensitive data from being logged in plain text. Intercepts all console methods (log, error, warn, etc.) and removes fields containing sensitive keywords before logging. Resolves issue where sensitive fields like tokens, passwords, private keys, and client credentials were exposed in plain text. Changes: - Added recursive sanitization with 18 sensitive keywords (token, bearer, privatekey, password, secret, client, oauth, mnemonic, seed, signature, otp, apikey, etc.) - Intercepts 9 console methods (log, error, warn, info, debug, dir, table, trace, assert) - Initialized console override in both entry points (bin/bitgo-express, src/expressApp.ts)
rishikeshdadam136
force-pushed
the
WP-7503
branch
from
dd3e889 to
5a4755d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket: WP-7503
Prevent sensitive data exposure in console logs
Implements automatic sanitization of console output to prevent sensitive data from being logged in plain text. Intercepts all console methods (log, error, warn, etc.) and removes fields containing sensitive keywords before logging. Resolves issue where sensitive fields like tokens, passwords, private keys, and client credentials were exposed in plain text.
Changes: