# CVE-2023-46575: SQL injection vulnerability in Meshery

> Remote attackers can exploit SQL injection in Meshery to retrieve sensitive data and execute arbitrary code via the order parameter.

- **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:** Yes
- **Published:** 24 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9jjc-grg5-67gj

## What is CVE-2023-46575?

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

### Official description

A SQL injection vulnerability exists in Meshery prior to version v0.6.179, enabling a remote attacker to retrieve sensitive information and execute arbitrary code through the “order” parameter

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

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

2 open source packages ship an affected version, including github.com/layer5io/meshery. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/layer5io/meshery` | Go | All versions | 0.6.179 |
| `github.com/layer5io/meshery` | Go | All versions | 0.6.179 |

Products: Layer5 Meshery.

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

Upgrade github.com/layer5io/meshery to 0.6.179 or later.

## Is CVE-2023-46575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-36535](https://insights.sbomify.com/CVE-2024-36535/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-31856](https://insights.sbomify.com/CVE-2021-31856/): SQL injection in n/a (critical 9.8)
- [CVE-2024-29031](https://insights.sbomify.com/CVE-2024-29031/): Meshery SQL Injection vulnerability (high 7.5)
- [CVE-2024-35181](https://insights.sbomify.com/CVE-2024-35181/): GHSL-2024-013 Meshery SQL Injection vulnerability (medium 5.9)
- [CVE-2024-35182](https://insights.sbomify.com/CVE-2024-35182/): GHSL-2024-014 Meshery SQL Injection vulnerability (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46575 is a critical SQL injection vulnerability in n/a, published on 24 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46575 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/layer5io/meshery (Go): affected all versions; fixed in 0.6.179
- github.com/layer5io/meshery (Go): affected all versions; fixed in 0.6.179

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

## Sources

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

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