Skip to content

Introduced protections against predictable RNG abuse - #1

Open
pixeebot[bot] wants to merge 1 commit into
mainfrom
pixeebot/drip-2023-12-26-pixee-java/secure-random
Open

Introduced protections against predictable RNG abuse#1
pixeebot[bot] wants to merge 1 commit into
mainfrom
pixeebot/drip-2023-12-26-pixee-java/secure-random

Conversation

@pixeebot

@pixeebot pixeebot Bot commented Dec 26, 2023

Copy link
Copy Markdown

This change replaces all new instances of java.util.Random with the marginally slower, but much more secure java.security.SecureRandom.

We have to work pretty hard to get computers to generate genuinely unguessable random bits. The java.util.Random type uses a method of pseudo-random number generation that unfortunately emits fairly predictable numbers.

If the numbers it emits are predictable, then it's obviously not safe to use in cryptographic operations, file name creation, token construction, password generation, and anything else that's related to security. In fact, it may affect security even if it's not directly obvious.

Switching to a more secure version is simple and our changes all look something like this:

- Random r = new Random();
+ Random r = new java.security.SecureRandom();
More reading

I have additional improvements ready for this repo! If you want to see them, leave the comment:

@pixeebot next

... and I will open a new PR right away!

Powered by: pixeebot (codemod ID: pixee:java/secure-random)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants