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

High 7.5 Published Updated

Attackers can bypass token validation in JHipster generator via timing attacks, allowing them to guess valid tokens and potentially access protected resources.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2015-20110?

CVE-2015-20110 is a high-severity vulnerability in n/a, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-307

Which versions are affected by CVE-2015-20110?

2 open source packages ship an affected version, including generator-jhipster. It affects 1 product.

PackageAffectedFixed in
generator-jhipster npmAll versions2.23.0
generator-jhipster npmAll versions2.23.0

Products include Jhipster Jhipster.

How do I fix CVE-2015-20110?

Upgrade generator-jhipster to 2.23.0 or later.

Is CVE-2015-20110 being exploited?

There is no known exploitation of CVE-2015-20110 in the wild and no public exploit code.

Sources

Also known as GHSA-4gpm-r23h-gprw.

Is CVE-2015-20110 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free