# CVE-2022-22300: Security feature bypass in Fortinet FortiManager, FortiAnalyzer

> Attackers can bypass device policies to force password changes for users in FortiAnalyzer and FortiManager, requiring administrators to upgrade to patched versions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C`)
- **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:** 1 Mar 2022
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-69m8-6m2p-9wrw

## What is CVE-2022-22300?

CVE-2022-22300 is a medium-severity vulnerability in Fortinet Fortianalyzer, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A improper handling of insufficient permissions or privileges in Fortinet FortiAnalyzer version 5.6.0 through 5.6.11, FortiAnalyzer version 6.0.0 through 6.0.11, FortiAnalyzer version 6.2.0 through 6.2.9, FortiAnalyzer version 6.4.0 through 6.4.7, FortiAnalyzer version 7.0.0 through 7 .0.2, FortiManager version 5.6.0 through 5.6.11, FortiManager version 6.0.0 through 6.0.11, FortiManager version 6.2.0 through 6.2.9, FortiManager version 6.4.0 through 6.4.7, FortiManager version 7.0.0 through 7.0.2 allows attacker to bypass the device policy and force the password-change action for its user.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 2 products.


Products: Fortinet Fortianalyzer, Fortinet Fortimanager.

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

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

## Is CVE-2022-22300 being exploited?

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

## Other vulnerabilities in Fortinet Fortianalyzer

- [CVE-2026-24858](https://insights.sbomify.com/CVE-2026-24858/): Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel (critical 9.4, exploited in the wild)
- [CVE-2023-25610](https://insights.sbomify.com/CVE-2023-25610/): Memory corruption in FortiAnalyzer (critical 9.3)
- [CVE-2021-32603](https://insights.sbomify.com/CVE-2021-32603/): Server-side request forgery in Fortinet FortiAnalyzer, FortiManager (high 8.8)
- [CVE-2020-12817](https://insights.sbomify.com/CVE-2020-12817/): Cross-site scripting in Fortinet FortiAnalyzer (high 8.8)
- [CVE-2024-48886](https://insights.sbomify.com/CVE-2024-48886/): Auth bypass in FortiOS (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22300 is a medium-severity vulnerability in Fortinet Fortianalyzer, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22300 in the wild and no public exploit code.

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

## Sources

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

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