You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,3 +21,21 @@ vulnerabilities.
21
21
22
22
This project has been used to generate PRs that automatically fix a security vulnerability in Maven POM files that
23
23
are using HTTP instead of HTTPS to resolve dependencies.
24
+
25
+
**Pull Requests Generated: 1,596**
26
+
27
+
## Project 2: CVE-2019-16303 - JHipster Vulnerability Fix - Use CSPRNG in RandomUtil
28
+
29
+
In 2019, I discovered a vulnerability in the [JHipster](https://www.jhipster.tech/) code generator where it was
30
+
generating vulnerable implementations of a class called `RandomUtil.java`.
31
+
32
+
Using one password reset token from these apps combined with the POC below, an attacker can determine all future password
33
+
reset tokens to be generated by these vulnerable servers.
34
+
This would allow an attacker to pick and choose what account they would like to takeover by sending account password reset requests for targeted accounts.
35
+
36
+
[POC code](http://web.archive.org/web/20191126104359/https://medium.com/@alex91ar/the-java-soothsayer-a-practical-application-for-insecure-randomness-c67b0cd148cd) has existed since March 3rd, 2018 for taking one RNG value generated by `RandomStringUtils` and reversing it to generate all of the past/future RNG values.
37
+
38
+
The fix was generated for each vulnerable file, preserving the original style of the file, by the [Rewrite project](https://github.com/openrewrite/rewrite).
39
+
See the specific code for this fix [here](https://github.com/moderneinc/jhipster-cwe-338).
0 commit comments