Skip to content
Fencer Intel
high 7.5

CVE-2015-9240 json

Authentication Weakness in keystone

published 2018-05-29 8 y ago modified 2026-06-17 4 mo ago also GHSA-39pj-gq8q-9pfj , EUVD-2018-0194

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

Summary

Due to a bug in the the default sign in functionality in the keystone node module before 0.3.16, incomplete email addresses could be matched. A correct password is still required to complete sign in.

Patch / fix

  • npm keystone 0.3.16
  • keystonejs keystone 0.3.16

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm keystone
<0.3.16
0.3.16

Affected products

  • HackerOne keystone node module

Classification

Weakness
  • CWE-255 Credentials Management Errors
  • CWE-1255 Comparison Logic is Vulnerable to Power Side-Channel Attacks

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.