CVE-2015-20110: High severity jhipster vulnerability

Published Oct 31, 2023
·
Updated

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 Software

2 affected componentsFixes available
npm/generator-jhipster<2.23.0
2.23.0
JHipster JHipster<2.23.0

Event History

Oct 31, 2023
CVE Published
12:00 AM
Data Sourced
12:00 AM
Description
Advisory Published
03:31 AM

Frequently Asked Questions

1

What is the vulnerability ID?

The vulnerability ID is CVE-2015-20110.

2

What is the severity of CVE-2015-20110?

The severity of CVE-2015-20110 is not specified in the provided information.

3

How does CVE-2015-20110 work?

CVE-2015-20110 allows a timing attack against validateToken by brute forcing one character at a time and observing the timing.

4

How can I fix CVE-2015-20110?

To fix CVE-2015-20110, update to version 2.23.0 or later of generator-jhipster.

5

Where can I find more information about CVE-2015-20110?

You can find more information about CVE-2015-20110 in the references provided: [link1], [link2], [link3].

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203