# CVE-2022-22302: Information disclosure in FortiAuthenticator

> A local attacker can retrieve private keys for push notification services from the filesystem, compromising secure communications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:U/RL:X/RC:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-vcgf-cp2m-h8gw

## What is CVE-2022-22302?

CVE-2022-22302 is a medium-severity vulnerability in Fortinet Fortios, published on 11 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A clear text storage of sensitive information (CWE-312) vulnerability in both FortiGate version 6.4.0 through 6.4.1, 6.2.0 through 6.2.9 and 6.0.0 through 6.0.13 and FortiAuthenticator version 5.5.0 and all versions of 6.1 and 6.0 may allow a local unauthorized party to retrieve the Fortinet private keys used to establish secure communication with both Apple Push Notification and Google Cloud Messaging services, via accessing the files on the filesystem.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 2 products.


Products: Fortinet Fortiauthenticator, Fortinet Fortios.

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

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

## Is CVE-2022-22302 being exploited?

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

## Other vulnerabilities in Fortinet Fortios

- [CVE-2026-44277](https://insights.sbomify.com/CVE-2026-44277/): Missing authorization in FortiAuthenticator (critical 9.1)
- [CVE-2013-6990](https://insights.sbomify.com/CVE-2013-6990/): Privilege escalation in n/a (critical 9.0)
- [CVE-2021-43067](https://insights.sbomify.com/CVE-2021-43067/): Information disclosure in Fortinet FortiAuthenticator (high 8.3)
- [CVE-2021-22124](https://insights.sbomify.com/CVE-2021-22124/): Denial of service in Fortinet FortiSandbox, FortiAuthenticator (high 7.5)
- [CVE-2015-1455](https://insights.sbomify.com/CVE-2015-1455/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22302 is a medium-severity vulnerability in Fortinet Fortios, published on 11 Jul 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-2022-22302 in the wild and no public exploit code.

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

## Sources

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

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