# CVE-2021-22128: Missing authorization in Fortinet FortiProxy

> Authenticated attackers can bypass access controls to reach internal ZebOS Shell via Quick Connection, enabling privilege escalation and potential code execution.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H`)
- **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:** 4 Mar 2021
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-mm5g-p9fc-43hm

## What is CVE-2021-22128?

CVE-2021-22128 is a high-severity missing authorization vulnerability in Fortinet Fortiproxy, published on 4 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper access control vulnerability in FortiProxy SSL VPN portal 2.0.0, 1.2.9 and below versions may allow an authenticated, remote attacker to access internal service such as the ZebOS Shell on the FortiProxy appliance through the Quick Connection functionality.

## Which versions are affected by CVE-2021-22128?

It affects 1 product.


Products: Fortinet Fortiproxy.

## How do I fix CVE-2021-22128?

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

## Is CVE-2021-22128 being exploited?

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

## Other vulnerabilities in Fortinet Fortiproxy

- [CVE-2022-41331](https://insights.sbomify.com/CVE-2022-41331/): Missing authorization in FortiPresence (critical 9.3)
- [CVE-2021-22130](https://insights.sbomify.com/CVE-2021-22130/): Memory corruption in Fortinet FortiProxy (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22128 and fix it if it is affected.

What it is: CVE-2021-22128 is a high-severity missing authorization vulnerability in Fortinet Fortiproxy, published on 4 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22128 in the wild and no public exploit code.

Affected product: Fortinet Fortiproxy. 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-2021-22128/ (Markdown: https://insights.sbomify.com/CVE-2021-22128/index.md)
```

## Sources

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

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