CVE-2015-20110: JHipster generator-jhipster before 2.23.0 allows a timing attack against validateToken due to a string compari

Q: How do I fix CVE-2015-20110?

jhipster: upgrade to 2.23.0. Exact commands for each OS are on this page.

Q: Is CVE-2015-20110 being exploited?

CVE-2015-20110 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2015-20110 affect?

CVE-2015-20110 affects jhipster. Severity is high (CVSS 7.5). 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 o

Q: How urgent is CVE-2015-20110?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2015-20110 is a high-severity flaw (CVSS 7.5) affecting jhipster. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-307
Published	2023-10-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jhipster

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-10-31 03:15 UTCPublished CVE record published
2026-06-17 00:23 UTCUpdated Record last modified

jhipster jhipster UPGRADE

Affected: < 2.23.0

Fixed in: 2.23.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jhipster || rpm -q jhipster || jhipster --version

2. UPGRADE to 2.23.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jhipster

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jhipster

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2015-20110?

jhipster: upgrade to 2.23.0. Exact commands for each OS are on this page.

Is CVE-2015-20110 being exploited?

CVE-2015-20110 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2015-20110 affect?

CVE-2015-20110 affects jhipster. Severity is high (CVSS 7.5). 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 o

How urgent is CVE-2015-20110?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs