Jhipster Kotlin
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Jhipster Kotlin.
By the Year
In 2026 there have been 0 vulnerabilities in Jhipster Kotlin. Jhipster Kotlin did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 9.80 |
It may take a day or so for new Jhipster Kotlin vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Jhipster Kotlin Security Vulnerabilities
A class generated by the Generator in JHipster before 6.3.0 and JHipster Kotlin through 1.1.0 produces code
CVE-2019-16303
9.8 - Critical
- September 14, 2019
A class generated by the Generator in JHipster before 6.3.0 and JHipster Kotlin through 1.1.0 produces code that uses an insecure source of randomness (apache.commons.lang3 RandomStringUtils). This allows an attacker (if able to obtain their own password reset URL) to compute the value for all other password resets for other accounts, thus allowing privilege escalation or account takeover.
PRNG
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Jhipster Kotlin or by Jhipster? Click the Watch button to subscribe.
