# CVE-2022-21555: Missing authorization in MySQL Server

> High-privileged local attackers can modify or read MySQL Shell data via GUI flaws, requiring user interaction and affecting VS Code extensions.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jul 2022
- **Updated:** 24 Sep 2024
- **Also known as:** BIT-mysql-shell-2022-21555, GHSA-jwmx-w668-p6cw

## What is CVE-2022-21555?

CVE-2022-21555 is a medium-severity missing authorization vulnerability in Oracle Corporation MySQL Server, published on 19 Jul 2022. 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

Vulnerability in the MySQL Shell for VS Code product of Oracle MySQL (component: Shell: GUI). Supported versions that are affected are 1.1.8 and prior. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Shell for VS Code executes to compromise MySQL Shell for VS Code. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Shell for VS Code, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Shell for VS Code accessible data as well as unauthorized read access to a subset of MySQL Shell for VS Code accessible data. CVSS 3.1 Base Score 4.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2022-21555?

1 open source package ship an affected version, including mysql-shell. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql-shell` | Bitnami | All versions | 1.1.9 |

Products: Oracle Mysql Shell.

## How do I fix CVE-2022-21555?

Upgrade mysql-shell to 1.1.9 or later.

## Is CVE-2022-21555 being exploited?

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

## Other vulnerabilities in Oracle Corporation MySQL Server

- [CVE-2026-46850](https://insights.sbomify.com/CVE-2026-46850/): Code injection in MySQL Shell (critical 9.9)
- [CVE-2026-46870](https://insights.sbomify.com/CVE-2026-46870/): Auth bypass in MySQL Shell (high 8.5)
- [CVE-2026-46869](https://insights.sbomify.com/CVE-2026-46869/): Cross-site request forgery in MySQL Shell (medium 6.5)
- [CVE-2026-46871](https://insights.sbomify.com/CVE-2026-46871/): Missing authorization in MySQL Shell (medium 6.5)
- [CVE-2022-21535](https://insights.sbomify.com/CVE-2022-21535/): Denial of service in MySQL Server (low 2.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21555 and fix it if it is affected.

What it is: CVE-2022-21555 is a medium-severity missing authorization vulnerability in Oracle Corporation MySQL Server, published on 19 Jul 2022. 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-2022-21555 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql-shell (Bitnami): affected all versions; fixed in 1.1.9

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

## Sources

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

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