# CVE-2023-42284: SQL injection in n/a

> An attacker can perform blind SQL injection via the api_version parameter to access and dump the database in Tyk Gateway.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-w8wr-v3q8-68hg

## What is CVE-2023-42284?

CVE-2023-42284 is a critical SQL injection vulnerability in n/a, published on 7 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Blind SQL injection in api_version parameter in Tyk Gateway version 5.0.3 allows attacker to access and dump the database via a crafted SQL query.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Tyk Tyk.

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

No fix has been published for CVE-2023-42284 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-42284 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42284 exists.

Public exploit code:

-   Proof of concept for CVE-2023-42284 in Tyk Gateway  (github_poc): https://github.com/andreysanyuk/CVE-2023-42284

## Other vulnerabilities in n/a

- [CVE-2023-42283](https://insights.sbomify.com/CVE-2023-42283/): SQL injection in n/a (critical 9.8)
- [CVE-2021-23357](https://insights.sbomify.com/CVE-2021-23357/): Directory Traversal (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42284 is a critical SQL injection vulnerability in n/a, published on 7 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42284 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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