dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Jul 2022. Known ransomware use
FortiproxyApplication · Fortinet

CVE-2018-13382

HIGH · 7.5 CVSS v3.1 Published 2019-06-04
Fix available
A fix is available. Upgrade to 1.2.9 / 5.4.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Authorization vulnerability in Fortinet FortiOS 6.0.0 to 6.0.4, 5.6.0 to 5.6.8 and 5.4.1 to 5.4.10 and FortiProxy 2.0.0, 1.2.0 to 1.2.8, 1.1.0 to 1.1.6, 1.0.0 to 1.0.7 under SSL VPN web portal allows an unauthenticated attacker to modify the password of an SSL VPN web portal user via specially crafted HTTP requests

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An improper authorization vulnerability in FortiOS and FortiProxy SSL VPN web portal allows unauthenticated attackers to modify user passwords via specially crafted HTTP requests. The vulnerability stems from missing authorization checks on password modification endpoints, enabling any unauthenticated user to reset arbitrary user credentials.

MitigationUpgrade FortiOS to version 6.0.5+, 5.6.9+, or 5.4.11+ and FortiProxy to version 1.0.8+, 1.1.7+, 1.2.9+, or 2.0.1+ per Fortinet advisory. Consider network access controls limiting SSL VPN portal exposure to trusted networks until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiproxyApplication
Affected:< 1.2.9= 2.0.0
FortiosOperating system
Affected:>= 5.4.1, < 5.4.11>= 5.6.0, < 5.6.9>= 6.0.0, < 6.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the product and version
    Determine if the system is running FortiOS or FortiProxy and obtain the installed firmware version. This can typically be retrieved from the system dashboard, CLI command 'get system status', or the admin web interface under System > Firmware or similar.
    Affected if The device is running FortiOS version 5.4.1 through 5.4.10, 5.6.0 through 5.6.8, or 6.0.0 through 6.0.4; or FortiProxy version 1.0.x, 1.1.x, 1.2.x before 1.2.9, or exactly version 2.0.0.
  2. Verify SSL VPN web portal is enabled
    Confirm that the SSL VPN web portal feature is configured on the device. Check the SSL-VPN settings in the web UI under VPN > SSL-VPN Portal or via CLI command 'show ssl-vpn web-proxy' or 'show ssl-vpn portal'.
    Affected if The SSL VPN web portal is configured and active on the device.
  3. Confirm SSL VPN portal is network accessible
    Verify that the SSL VPN web portal is reachable from untrusted networks. Check firewall policies and interface bindings that expose the SSL VPN service (typically TCP port 443 or 10443) to external or untrusted networks.
    Affected if The SSL VPN portal is exposed to the internet or untrusted networks without adequate access controls.

If the device runs a vulnerable FortiOS or FortiProxy version AND has the SSL VPN web portal enabled AND is network-accessible to untrusted users, then the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.9 / 5.4.11 / 5.6.9 or later
Fixed in 1.2.95.4.115.6.9
Interim mitigation

Upgrade FortiOS to version 6.0.5+, 5.6.9+, or 5.4.11+ and FortiProxy to version 1.0.8+, 1.1.7+, 1.2.9+, or 2.0.1+ per Fortinet advisory. Consider network access controls limiting SSL VPN portal exposure to trusted networks until patching is complete.

Recommended fix High confidence

FortiOS 5.4.11+, 5.6.9+, or 6.0.5+ | FortiProxy 1.2.9+ or 2.0.1+

  1. 1. Identify the currently installed FortiOS or FortiProxy version and build number in the device CLI using 'get system status' or via the web UI
  2. 2. For FortiOS 5.4.x: Plan upgrade to FortiOS 5.4.11 or later (5.6.9+ or 6.0.5+ recommended for latest features)
  3. 3. For FortiOS 5.6.x: Plan upgrade to FortiOS 5.6.9 or later (6.0.5+ recommended)
  4. 4. For FortiOS 6.0.x: Plan upgrade to FortiOS 6.0.5 or later
  5. 5. For FortiProxy 1.x: Plan upgrade to FortiProxy 1.2.9 or later
  6. 6. For FortiProxy 2.0.0: Plan upgrade to FortiProxy 2.0.1 or later
  7. 7. Download the appropriate firmware image from support.fortinet.com
  8. 8. Back up the current configuration
Caveat Standard firmware upgrade risks apply - backup configuration before upgrading; review release notes for minor behavioral changes between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiproxy Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13382 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data