authentikat-jwt up to 0.4.5 JsonWebToken.scala JsonWebTokenvalidate Request 7pk time and state
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in authentikat-jwt up to 0.4.5. This affects the function JsonWebTokenvalidate of the file main/scala/authentikat/jwt/JsonWebToken.scala. This manipulation as part of Request causes 7pk time and state.
This vulnerability is tracked as CVE-2017-18239. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in authentikat-jwt up to 0.4.5 and classified as critical. Affected by this vulnerability is the function JsonWebTokenvalidate of the file main/scala/authentikat/jwt/JsonWebToken.scala. The manipulation as part of a Request leads to a 7pk time and state vulnerability. The CWE definition for the vulnerability is CWE-361. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests.
The bug was discovered 03/17/2018. The weakness was disclosed 03/18/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2017-18239 since 03/17/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.6VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.4
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: 7pk time and stateCWE: CWE-361
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
03/17/2018 🔍03/17/2018 🔍
03/17/2018 🔍
03/18/2018 🔍
03/18/2018 🔍
02/22/2023 🔍
Sources
Advisory: 2d2fa0d40ac8f2f7aa7e9b070fa1a25eee082cb0Status: Not defined
CVE: CVE-2017-18239 (🔍)
GCVE (CVE): GCVE-0-2017-18239
GCVE (VulDB): GCVE-100-114727
Entry
Created: 03/18/2018 10:24Updated: 02/22/2023 10:37
Changes: 03/18/2018 10:24 (56), 01/14/2020 16:08 (1), 02/22/2023 10:30 (4), 02/22/2023 10:37 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.