# CVE-2018-13374: Fortinet FortiOS and FortiADC Improper Access Control

> An attacker can steal LDAP credentials by redirecting connectivity tests to a rogue server, exposing sensitive configuration data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 8 Sep 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2019
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-rpmq-q4mw-pc44

## What is CVE-2018-13374?

CVE-2018-13374 is a medium-severity vulnerability in Fortinet Fortios, published on 22 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Improper Access Control in Fortinet FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4 allows attacker to obtain the LDAP server login credentials configured in FortiGate via pointing a LDAP server connectivity test request to a rogue LDAP server instead of the configured one.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-13374?

It affects 2 products.


Products: Fortinet Fortiadc, Fortinet Fortios.

## How do I fix CVE-2018-13374?

No fix has been published for CVE-2018-13374 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Sep 2022.

## Is CVE-2018-13374 being exploited?

Yes. Attackers have exploited CVE-2018-13374 in the wild since at least 8 Sep 2022, including in ransomware campaigns.

Public exploit code:

- Fortinet FortiGate FortiOS < 6.0.3 - LDAP Credential Disclosure (exploitdb)
- Conducted a full SOC investigation into a Conti ransomware compromise of an Exchange server using Splunk 8.2.2. Analysed 28,145 events across Windows Security, Sysmon, and IIS log sources to reconstruct the complete attack chain. Identified three exploited CVEs (CVE-2020-0796, CVE-2018-13374, CVE-2018-13379), located a trojanised cmd.exe  (github_poc): https://github.com/Justjeff211/conti-ransomware-writeup

## Other vulnerabilities in Fortinet Fortios

- [CVE-2022-38374](https://insights.sbomify.com/CVE-2022-38374/): Cross-site scripting in Fortinet FortiADC (high 8.8)
- [CVE-2023-37933](https://insights.sbomify.com/CVE-2023-37933/): Cross-site scripting in FortiADC (high 8.6)
- [CVE-2022-39947](https://insights.sbomify.com/CVE-2022-39947/): Command injection in FortiADC (high 8.6)
- [CVE-2022-35851](https://insights.sbomify.com/CVE-2022-35851/): Cross-site scripting in Fortinet FortiADC (high 8.0)
- [CVE-2023-26205](https://insights.sbomify.com/CVE-2023-26205/): Privilege escalation in FortiADC (high 7.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13374 and fix it if it is affected.

What it is: CVE-2018-13374 is a medium-severity vulnerability in Fortinet Fortios, published on 22 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-13374 in the wild since at least 8 Sep 2022, including in ransomware campaigns.

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-2018-13374/ (Markdown: https://insights.sbomify.com/CVE-2018-13374/index.md)
```

## Sources

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

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