CVE-2015-20110
Jhipster vulnerability
JHipster generator-jhipster before 2.23.0 allows a timing attack against validateToken due to a string comparison that stops at the first character that is different. Attackers can guess tokens by brute forcing one character at a time and observing the timing. This of course drastically reduces the search space to a linear amount of guesses based on the token length times the possible characters.
Affected products
Jhipster. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Jhipster runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/jhipster/generator-jhipster/issues/2095 · Patch
- github.com/jhipster/generator-jhipster/commit/79fe5626cb1bb80f9ac86cf46980748e65d2bdbc · Patch
- github.com/jhipster/generator-jhipster/commit/7c49ab3d45dc4921b831a2ca55fb1e2a2db1ee25 · Patch
- github.com/jhipster/generator-jhipster/compare/v2.22.0...v2.23.0 · Patch
- nvd.nist.gov/vuln/detail/CVE-2015-20110
- cve.org/CVERecord?id=CVE-2015-20110
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.