JWT is a library to work with JSON Web Token and JSON Web Signature. Prior to versions 3.4.6, 4.0.4, and 4.1.5, users of HMAC-based algorithms (HS256, HS384, and HS512) combined with LcobucciJWTSignerKeyLocalFileReference as key are having their tokens issued/validated using the file path as hashing key - instead of the contents. The HMAC hashing functions take any string as input and, since users can issue and validate tokens, users are lead to believe that everything works properly. Versions 3.4.6, 4.0.4, and 4.1.5 have been patched to always load the file contents, deprecated the LcobucciJWTSignerKeyLocalFileReference, and suggest LcobucciJWTSignerKeyInMemory as the alternative. As a workaround, use LcobucciJWTSignerKeyInMemory instead of LcobucciJWTSignerKeyLocalFileReference to create the instances of ones keys.
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jwt | Jwt_project | 3.4.0 (including) | 3.4.6 (excluding) |
| Jwt | Jwt_project | 4.0.0 (including) | 4.0.4 (excluding) |
| Jwt | Jwt_project | 4.1.0 (including) | 4.1.5 (excluding) |