# CVE-2021-32589: Use after free in FortiAnalyzer

> Remote unauthenticated attackers can execute arbitrary code as root on FortiManager and FortiAnalyzer devices via a crafted request to the fgfm port.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** GHSA-5mvx-j4j8-xv4p

## What is CVE-2021-32589?

CVE-2021-32589 is a high-severity use after free vulnerability in Fortinet Fortianalyzer, published on 19 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use After Free (CWE-416) vulnerability in FortiManager version 7.0.0, version 6.4.5 and below, version 6.2.7 and below, version 6.0.10 and below, version 5.6.10 and below, version 5.4.7 and below, version 5.2.10 and below, version 5.0.12 and below and FortiAnalyzer version 7.0.0, version 6.4.5 and below, version 6.2.7 and below, version 6.0.10 and below, version 5.6.10 and below, version 5.4.7 and below, version 5.3.11, version 5.2.10 to 5.2.4 fgfmsd daemon may allow a remote, non-authenticated attacker to execute unauthorized code as root via sending a specifically crafted request to the fgfm port of the targeted device.

Weakness: CWE-416 (Use After Free)

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

It affects 3 products.


Products: Fortinet Fortianalyzer, Fortinet Fortimanager, Fortinet Fortiportal.

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

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

## Is CVE-2021-32589 being exploited?

There is no known exploitation of CVE-2021-32589 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-2021-32589 and fix it if it is affected.

What it is: CVE-2021-32589 is a high-severity use after free vulnerability in Fortinet Fortianalyzer, published on 19 Dec 2024. 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-2021-32589 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-2021-32589/ (Markdown: https://insights.sbomify.com/CVE-2021-32589/index.md)
```

## Sources

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

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