Web-Token jwt-framework before 3.4.10 DoS via Unbounded PBES2 p2c Iteration Count
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| web-token | jwt-library | unaffected |
|
|||||||||
| web-token | jwt-library | unaffected |
|
|||||||||
| web-token | jwt-library | unaffected |
|
|||||||||
| web-token | jwt-framework | unaffected |
|
|||||||||
| web-token | jwt-framework | unaffected |
|
|||||||||
| web-token | jwt-framework | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Web-Token jwt-framework and jwt-library before 3.4.10, 4.0.0 before 4.0.7, and 4.1.0 before 4.1.7 contain an uncontrolled resource consumption vulnerability in PBES2AESKW::unwrapKey(), which passes the attacker-controlled p2c JWE header value to hash_pbkdf2() without an upper bound. Unauthenticated attackers can send a JWE using a PBES2-HS*+A*KW algorithm with a huge p2c iteration count to force lengthy PBKDF2 computations and exhaust server CPU. | |
| Title | Web-Token jwt-framework before 3.4.10 DoS via Unbounded PBES2 p2c Iteration Count | |
| First Time appeared |
Nats
Nats jwt Library |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:nats:jwt_library:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Nats
Nats jwt Library |
|
| References |
| |
| Metrics |
cvssV3_1
|