# CVE-2023-30605: Multiple SQL injections in sql/instance.py param_edit method in Archery - GHSL-2022-104

> Attackers can inject SQL via variable parameters to query connected databases in the Archery SQL audit platform.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-6mqc-w2qp-fvhp

## What is CVE-2023-30605?

CVE-2023-30605 is a medium-severity SQL injection vulnerability in hhyo Archery, published on 18 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Archery is an open source SQL audit platform. The Archery project contains multiple SQL injection vulnerabilities, that may allow an attacker to query the connected databases. User input coming from the `variable_name` and `variable_value` parameter value in the `sql/instance.py` `param_edit` endpoint is passed to a set of methods in given SQL engine implementations, which concatenate user input unsafely into a SQL query and afterwards pass it to the `query` method of each database engine for execution. The affected methods are: `set_variable` in `sql/engines/goinception.py` which concatenates input which is passed to execution on the database in the `sql/engines/goinception.py`, `get_variables` in `sql/engines/goinception.py`  which concatenates input which is passed to execution on the database in the `sql/engines/goinception.py`, `set_variable` in `sql/engines/mysql.py`  which concatenates input which is passed to execution on the database in the `sql/engines/mysql.py` `query`, and `get_variables` in `sql/engines/mysql.py`which concatenates input which is passed to execution on the database in the `sql/engines/mysql.py` `query`. Each of these issues may be mitigated by escaping user input or by using prepared statements when executing SQL queries. This advisory is also indexed as `GHSL-2022-104`.

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

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

It affects 1 product.


Products: Archerydms Archery.

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

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

## Is CVE-2023-30605 being exploited?

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

## Other vulnerabilities in hhyo Archery

- [CVE-2022-38537](https://insights.sbomify.com/CVE-2022-38537/): SQL injection in n/a (critical 9.8)
- [CVE-2022-38538](https://insights.sbomify.com/CVE-2022-38538/): SQL injection in n/a (critical 9.8)
- [CVE-2022-38539](https://insights.sbomify.com/CVE-2022-38539/): SQL injection in n/a (critical 9.8)
- [CVE-2022-38540](https://insights.sbomify.com/CVE-2022-38540/): SQL injection in n/a (critical 9.8)
- [CVE-2022-38541](https://insights.sbomify.com/CVE-2022-38541/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30605 is a medium-severity SQL injection vulnerability in hhyo Archery, published on 18 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30605 exists.

Affected product: hhyo Archery. 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-30605/ (Markdown: https://insights.sbomify.com/CVE-2023-30605/index.md)
```

## Sources

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

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