Description
In Firebase PHP-JWT before 6.0.0, an algorithm-confusion issue (e.g., RS256 / HS256) exists via the kid (aka Key ID) header, when multiple types of keys are loaded in a key ring. This allows an attacker to forge tokens that validate under the incorrect key. NOTE: this provides a straightforward way to use the PHP-JWT library unsafely, but might not be considered a vulnerability in the library itself.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-1387 | In Firebase PHP-JWT before 6.0.0, an algorithm-confusion issue (e.g., RS256 / HS256) exists via the kid (aka Key ID) header, when multiple types of keys are loaded in a key ring. This allows an attacker to forge tokens that validate under the incorrect key. NOTE: this provides a straightforward way to use the PHP-JWT library unsafely, but might not be considered a vulnerability in the library itself. |
Github GHSA |
GHSA-8xf4-w7qw-pjjw | Firebase PHP-JWT key/algorithm type confusion |
References
| Link | Providers |
|---|---|
| https://github.com/firebase/php-jwt/issues/351 |
|
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T05:17:41.727Z
Reserved: 2022-03-29T00:00:00.000Z
Link: CVE-2021-46743
No data.
Status : Modified
Published: 2022-03-29T07:15:07.017
Modified: 2024-11-21T06:34:37.197
Link: CVE-2021-46743
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA