{"answers":{"affected":"2 open source packages ship an affected version, including graphql-shield.","exploited":"There is no known exploitation of GHSA-hx78-272p-mqqh in the wild and no public exploit code.","fix":"Upgrade graphql-shield to 6.0.6 or later.","what":"GHSA-hx78-272p-mqqh is an authentication bypass vulnerability in graphql-shield, published on 3 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-hx78-272p-mqqh and fix it if it is affected.\n\nWhat it is: GHSA-hx78-272p-mqqh is an authentication bypass vulnerability in graphql-shield, published on 3 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-hx78-272p-mqqh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- graphql-shield (npm): affected all versions; fixed in 6.0.6\n- graphql-shield (npm): affected all versions; fixed in 6.0.6\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-hx78-272p-mqqh/ (Markdown: https://insights.sbomify.com/GHSA-hx78-272p-mqqh/index.md)","id":"GHSA-hx78-272p-mqqh","markdown":"https://insights.sbomify.com/GHSA-hx78-272p-mqqh/index.md","name":"GHSA-hx78-272p-mqqh","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"GraphQL authorization library","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in graphql-shield due to insecure caching keys, potentially accessing unauthorized data.","user_interaction":"not_required","vuln_class":"auth_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 `graphql-shield` prior to 6.0.6 are vulnerable to an Authorization Bypass. The rule caching option `no_cache` relies on keys generated by cryptographically insecure functions, which may cause rules to be incorrectly cached. This allows attackers to access information they should not have access to in case of a key collision.\n\n## Recommendation\n\nUpgrade to version 6.0.6 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":"Authorization Bypass in graphql-shield","id":"GHSA-hx78-272p-mqqh","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["6.0.6"],"introduced":["0"],"last_affected":[],"package":"graphql-shield","purl":null,"source":"GHSA-hx78-272p-mqqh"},{"ecosystem":"npm","fixed":["6.0.6"],"introduced":["0"],"last_affected":[],"package":"graphql-shield","purl":"pkg:npm/graphql-shield","source":"GHSA-hx78-272p-mqqh"}],"products":null,"published":"2020-09-03","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":"Attackers can bypass authorization checks in graphql-shield due to insecure caching keys, potentially accessing unauthorized data.","url":"https://insights.sbomify.com/GHSA-hx78-272p-mqqh/"}