web-token jwt-framework 1.2.0 before 3.4.10 Missing Authentication in Chacha20Poly1305 Key Encryption
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-experimental | unaffected |
|
|||||||||
| web-token | jwt-experimental | unaffected |
|
|||||||||
| web-token | jwt-experimental | 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 1.2.0 before 3.4.10, jwt-experimental before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 contain a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm, which discards the Poly1305 tag in encryptKey() and calls openssl_decrypt() without it in decryptKey(). Attackers on the token path can modify the encrypted content encryption key undetected. | |
| Title | web-token jwt-framework 1.2.0 before 3.4.10 Missing Authentication in Chacha20Poly1305 Key Encryption | |
| Weaknesses | CWE-353 | |
| References |
| |
| Metrics |
cvssV3_1
|