# CVE-2023-34247: @keystone-6/auth Open Redirect vulnerability

> Attackers can redirect users to malicious external sites by bypassing the redirect filter in the Keystone auth package.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-jqxr-vjvv-899m

## What is CVE-2023-34247?

CVE-2023-34247 is a medium-severity vulnerability in keystonejs keystone, published on 13 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Keystone is a content management system for Node.JS. There is an open redirect in the `@keystone-6/auth` package versions 7.0.0 and prior, where the redirect leading `/` filter can be bypassed. Users may be redirected to domains other than the relative host, thereby it might be used by attackers to re-direct users to an unexpected location. To mitigate this issue, one may apply a patch from pull request 8626 or avoid using the `@keystone-6/auth` package.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2023-34247?

2 open source packages ship an affected version, including @keystone-6/auth. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@keystone-6/auth` | npm | All versions | 7.0.0 |
| `@keystone-6/auth` | npm | All versions | 7.0.0 |

Products: Keystonejs Keystone.

## How do I fix CVE-2023-34247?

Upgrade @keystone-6/auth to 7.0.0 or later.

## Is CVE-2023-34247 being exploited?

There is no known exploitation of CVE-2023-34247 in the wild and no public exploit code.

## Other vulnerabilities in keystonejs keystone

- [CVE-2022-39382](https://insights.sbomify.com/CVE-2022-39382/): NODE_ENV in Keystone defaults to development with esbuild (critical 9.8)
- [CVE-2022-29354](https://insights.sbomify.com/CVE-2022-29354/): File upload in n/a (critical 9.8)
- [CVE-2022-39322](https://insights.sbomify.com/CVE-2022-39322/): @keystone-6/core vulnerable to field-level access-control bypass for multiselect field (critical 9.1)
- [CVE-2017-16570](https://insights.sbomify.com/CVE-2017-16570/): Cross-Site Request Forgery (CSRF) in keystone (high 8.8)
- [CVE-2017-15879](https://insights.sbomify.com/CVE-2017-15879/): Keystone is vulnerable to CSV injection (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34247 and fix it if it is affected.

What it is: CVE-2023-34247 is a medium-severity vulnerability in keystonejs keystone, published on 13 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-34247 in the wild and no public exploit code.

Affected packages and fixed versions:
- @keystone-6/auth (npm): affected all versions; fixed in 7.0.0
- @keystone-6/auth (npm): affected all versions; fixed in 7.0.0

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/CVE-2023-34247/ (Markdown: https://insights.sbomify.com/CVE-2023-34247/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34247
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34247
- OSV: https://osv.dev/vulnerability/CVE-2023-34247

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34247/
Summaries are generated and may contain mistakes; the official description above is the record.