{"answers":{"affected":"2 open source packages ship an affected version, including firebase/php-jwt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-46743 in the wild and no public exploit code.","fix":"Upgrade firebase/php-jwt to 6.0.0 or later.","what":"CVE-2021-46743 is a critical vulnerability in n/a, published on 29 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-46743 and fix it if it is affected.\n\nWhat it is: CVE-2021-46743 is a critical vulnerability in n/a, published on 29 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-46743 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- firebase/php-jwt (Packagist): affected all versions; fixed in 6.0.0\n- firebase/php-jwt (Packagist): affected all versions; fixed in 6.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-46743/ (Markdown: https://insights.sbomify.com/CVE-2021-46743/index.md)","id":"CVE-2021-46743","markdown":"https://insights.sbomify.com/CVE-2021-46743/index.md","name":"CVE-2021-46743","record":{"aliases":["GHSA-8xf4-w7qw-pjjw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP JWT library","requires_auth":"none","summary":"Attackers can forge JWT tokens by exploiting algorithm confusion in the kid header when multiple key types are loaded, bypassing authentication.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"firebase_php-jwt","vendor":"google"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Firebase PHP-JWT key/algorithm type confusion","id":"CVE-2021-46743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in AMD Processors","id":"CVE-2021-46744"},"packages":[{"ecosystem":"Packagist","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"firebase/php-jwt","purl":null,"source":"GHSA-8xf4-w7qw-pjjw"},{"ecosystem":"Packagist","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"firebase/php-jwt","purl":"pkg:composer/firebase/php-jwt","source":"GHSA-8xf4-w7qw-pjjw"}],"prev":{"headline":"Missing authorization in EMUI","id":"CVE-2021-46742"},"products":["n/a"],"published":"2022-03-29","related":[{"cvss_score":6.5,"headline":"php-jwt contains weak encryption","id":"CVE-2025-45769","kev_date_added":null,"published":"2025-07-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can forge JWT tokens by exploiting algorithm confusion in the kid header when multiple key types are loaded, bypassing authentication.","url":"https://insights.sbomify.com/CVE-2021-46743/"}