CVE-2017-18486 json
Jitbit Helpdesk before 9.0.3 allows remote attackers to escalate privileges because of mishandling of the User/AutoLogin userHash parameter.
published 2019-08-09 7 y ago modified 2026-06-17 4 mo ago also EUVD-2017-9602
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.8%
- EPSS 4.8% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Jitbit Helpdesk before 9.0.3 allows remote attackers to escalate privileges because of mishandling of the User/AutoLogin userHash parameter. By inspecting the token value provided in a password reset link, a user can leverage a weak PRNG to recover the shared secret used by the server for remote authentication. The shared secret can be used to escalate privileges by forging new tokens for any user. These tokens can be used to automatically log in as the affected user.
Patch / fix
- jitbit helpdesk 9.0.3
Exploit prediction
4.81% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Kc57/JitBit_Helpdesk_Auth_Bypass referenced PoC, tagged "exploit" by a source, unverified
- exploit-db.com https://www.exploit-db.com/exploits/42776 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-332 Insufficient Entropy in PRNG
References
-
github.com
/Kc57/JitBit_Helpdesk_Auth_Bypass
exploit, third-party-advisory
-
exploit-db.com
/exploits/42776
exploit, third-party-advisory, vdb-entry
-
trustedsec.com
/2017/09/full-disclosure-jitbit-helpdesk-authentication-bypass-0-day
third-party-advisory
-
packetstormsecurity.com
/files/144334/JitBit-Helpdesk-9.0.2-Broken-Authentication.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2017-18486
- NVD CVE-2017-18486
Fencer Vulns 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.