Potential fix for code scanning alert no. 2: Insecure randomness #43
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.
Potential fix for https://github.com/dev-asterix/PgStudio/security/code-scanning/2
To fix this issue, we should replace the use of
Math.random()for generating session IDs with a cryptographically secure random value source. In Node.js (including VSCode extensions), this is best achieved with thecryptomodule'srandomBytes()function, which provides CSPRNG output. We'll importcryptoat the top, and update thegenerateSessionIdmethod to usecrypto.randomBytes(), base64-encoded (or hex-encoded) for the unique suffix, in place of the insecureMath.random(). No other code changes are needed, as the functionality of generating a unique session ID with a timestamp and random suffix remains identical.Suggested fixes powered by Copilot Autofix. Review carefully before merging.