{"answers":{"affected":"2 open source packages ship an affected version, including jwt-simple.","exploited":"There is no known exploitation of GHSA-8v5f-hp78-jgxq in the wild and no public exploit code.","fix":"Upgrade jwt-simple to 0.5.3 or later.","what":"GHSA-8v5f-hp78-jgxq is a vulnerability in jwt-simple, published on 6 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-8v5f-hp78-jgxq and fix it if it is affected.\n\nWhat it is: GHSA-8v5f-hp78-jgxq is a vulnerability in jwt-simple, published on 6 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-8v5f-hp78-jgxq in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jwt-simple (npm): affected all versions; fixed in 0.5.3\n- jwt-simple (npm): affected all versions; fixed in 0.5.3\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/GHSA-8v5f-hp78-jgxq/ (Markdown: https://insights.sbomify.com/GHSA-8v5f-hp78-jgxq/index.md)","id":"GHSA-8v5f-hp78-jgxq","markdown":"https://insights.sbomify.com/GHSA-8v5f-hp78-jgxq/index.md","name":"GHSA-8v5f-hp78-jgxq","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js JWT library","requires_auth":"none","summary":"An attacker can bypass JWT signature verification by exploiting algorithm confusion, allowing unauthorized access to protected resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Versions of `jwt-simple` prior to 0.5.3 are vulnerable to Signature Verification Bypass. If no algorithm is specified in the `decode()` function, the packages uses the algorithm in the JWT to decode tokens. This allows an attacker to create a HS256 (symmetric algorithm) JWT with the server's public key as secret, and the package will verify it as HS256 instead of RS256 (asymmetric algorithm).\n\n## Recommendation\n\nUpgrade to version 0.5.3 or later.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Signature Verification Bypass in jwt-simple","id":"GHSA-8v5f-hp78-jgxq","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"jwt-simple","purl":null,"source":"GHSA-8v5f-hp78-jgxq"},{"ecosystem":"npm","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"jwt-simple","purl":"pkg:npm/jwt-simple","source":"GHSA-8v5f-hp78-jgxq"}],"products":null,"published":"2019-06-06","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can bypass JWT signature verification by exploiting algorithm confusion, allowing unauthorized access to protected resources.","url":"https://insights.sbomify.com/GHSA-8v5f-hp78-jgxq/"}