Skip to content
Fencer Intel
high 7.5

CVE-2015-20110 json

generator-jhipster allows a timing attack against validateToken due to a string comparison that stops at the first character

published 2023-10-31 3 y ago modified 2026-06-17 4 mo ago also GHSA-4gpm-r23h-gprw , EUVD-2023-2645

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm generator-jhipster 2.23.0
  • jhipster jhipster 2.23.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm generator-jhipster
<2.23.0
2.23.0

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.