fix(security): Remove sensitive auth data from console logs#6700
Open
shakecodeslikecray wants to merge 1 commit intoChatGPTNextWeb:mainfrom
Open
fix(security): Remove sensitive auth data from console logs#6700shakecodeslikecray wants to merge 1 commit intoChatGPTNextWeb:mainfrom
shakecodeslikecray wants to merge 1 commit intoChatGPTNextWeb:mainfrom
Conversation
Bug ID: WR-001 File: app/api/auth.ts:36 Severity: medium Access codes and hashed access codes are logged to the console, which could expose authentication secrets in logs. The code logs allowed hashed codes, the raw access code, the hashed access code, and user IP addresses. Fixed by whiterose
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
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.
Summary
Problem
In
app/api/auth.ts:33-37, the following sensitive information was being logged to the console:This is a security risk as these values could be exposed in:
Fix
Removed all sensitive data logging, keeping only a simple timestamp for debugging:
Test plan
🤖 Generated with Claude Code
Bug discovered by whiterose