CVE-2015-20110Not scoredCWE-307

CVE-2015-20110: Jhipster vulnerability

Jhipster

Affected: Jhipster · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.7%probability of exploitation in the next 30 days

54th percentile

050100

Higher than 54% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Restriction of Excessive Authentication Attempts · Authentication
Vendor: Jhipster
Published: October 2023
Band: Unlikely (under 1%), October 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2015-20110 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.