Fix CodeQL Password in configuration file Rule False Positives #105
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
…deQL rule id cs/password-in-configuration false positive
This was referenced Aug 19, 2025
This was referenced Nov 11, 2025
This was referenced Jan 7, 2026
This was referenced Jan 27, 2026
This was referenced Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CodeQL is falsly identifying the documentation examples of SQL Server connection strings violating CodeQL: c# Password in configuration file Rule. Even though it's a false positive, many organizations take stances of not allowing dismissals and would rather see fixes for CodeQL findings. This proposed change will prevent this rule from being tripped in the future and not require organizations to mark these as false positives manually.