# GHSA-hx78-272p-mqqh: Authorization Bypass in graphql-shield

> Attackers can bypass authorization checks in graphql-shield due to insecure caching keys, potentially accessing unauthorized data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-hx78-272p-mqqh?

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.

### Official 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.

## Recommendation

Upgrade to version 6.0.6 or later.

## Which versions are affected by GHSA-hx78-272p-mqqh?

2 open source packages ship an affected version, including graphql-shield.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `graphql-shield` | npm | All versions | 6.0.6 |
| `graphql-shield` | npm | All versions | 6.0.6 |

## How do I fix GHSA-hx78-272p-mqqh?

Upgrade graphql-shield to 6.0.6 or later.

## Is GHSA-hx78-272p-mqqh being exploited?

There is no known exploitation of GHSA-hx78-272p-mqqh in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hx78-272p-mqqh and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of GHSA-hx78-272p-mqqh in the wild and no public exploit code.

Affected packages and fixed versions:
- graphql-shield (npm): affected all versions; fixed in 6.0.6
- graphql-shield (npm): affected all versions; fixed in 6.0.6

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-hx78-272p-mqqh/ (Markdown: https://insights.sbomify.com/GHSA-hx78-272p-mqqh/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hx78-272p-mqqh

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hx78-272p-mqqh/
Summaries are generated and may contain mistakes; the official description above is the record.