# CVE-2021-41019: Information disclosure in Fortinet FortiOS

> Improper certificate validation in FortiOS allows connecting to malicious LDAP servers via GUI options, leading to disclosure of sensitive Active Directory credentials.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:U/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Nov 2021
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-hj73-5q9f-3jj4

## What is CVE-2021-41019?

CVE-2021-41019 is a low-severity vulnerability in Fortinet Fortios, published on 2 Nov 2021. 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

An improper validation of certificate with host mismatch [CWE-297] vulnerability in FortiOS versions 6.4.6 and below may allow the connection to a malicious LDAP server via options in GUI, leading to disclosure of sensitive information, such as AD credentials.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Fortinet Fortios.

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

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

## Is CVE-2021-41019 being exploited?

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

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41019 is a low-severity vulnerability in Fortinet Fortios, published on 2 Nov 2021. 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-2021-41019 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-2021-41019/ (Markdown: https://insights.sbomify.com/CVE-2021-41019/index.md)
```

## Sources

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

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