hapi-auth-jwt2 5.1.1 on Node.js Try Authentication improper authentication
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in hapi-auth-jwt2 5.1.1 on Node.js. This issue affects some unknown processing of the component Try Authentication. The manipulation leads to improper authentication. The identification of this vulnerability is CVE-2016-10525. The attack may be initiated remotely. There is no exploit available. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability classified as critical was found in hapi-auth-jwt2 5.1.1 on Node.js (JavaScript Library). This vulnerability affects some unknown processing of the component Try Authentication. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
When attempting to allow authentication mode `try` in hapi, hapi-auth-jwt2 version 5.1.1 introduced an issue whereby people could bypass authentication.
The bug was discovered 01/28/2016. The weakness was released 05/29/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2016-10525 since 10/29/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 852 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
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
01/28/2016 🔍10/29/2017 🔍
05/29/2018 🔍
05/29/2018 🔍
05/30/2018 🔍
03/17/2023 🔍
Sources
Advisory: 111Status: Not defined
CVE: CVE-2016-10525 (🔍)
GCVE (CVE): GCVE-0-2016-10525
GCVE (VulDB): GCVE-100-118306
Entry
Created: 05/30/2018 08:47 AMUpdated: 03/17/2023 02:59 PM
Changes: 05/30/2018 08:47 AM (58), 02/09/2020 03:28 PM (1), 03/17/2023 02:59 PM (4)
Complete: 🔍
Cache ID: 18:49D:40
No comments yet. Languages: en.
Please log in to comment.