✨ (Snyk) Fixed finding: "java/InsecureSecret" #44
+3
−2
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.



Pixee Fix ID: 45d2119c-51ee-4583-b089-6bfe653918da
Confidence: LOW
Fix confidence is a rating derived from an internal benchmark and includes High, Medium, and Low confidence fixes. It comprises three weighted scores reflecting the safety, effectiveness and cleanliness of Pixee's code changes within a fix. View Details in Pixee.
✨✨✨
Remediation
This change fixes "java/InsecureSecret" (id = java/InsecureSecret) identified by Snyk.
Details
Use of Insufficiently Random Values can expose applications to various security risks, such as predictable outcomes that can be exploited by attackers. The fix involved replacing the usage of
new Random()withSecureRandomto utilize a cryptographically secure PRNG, ensuring randomness quality suitable for cryptographic use.