CVE-2015-20110

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-10-31 03:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-10-31 03:15 UTC

Last modified

2026-06-17 00:23 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-307

Record status

Modified

Affected

• Jhipster < 2.23.0

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2015-20110.md and follow it. Check whether this project is affected by CVE-2015-20110. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge