dbcve.org
FortiosOperating system · Fortinet

CVE-2017-14182

MEDIUM · 6.5 CVSS v3.0 Published 2017-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A Denial of Service (DoS) vulnerability in Fortinet FortiOS 5.4.0 to 5.4.5 allows an authenticated user to cause the web GUI to be temporarily unresponsive, via passing a specially crafted payload to the 'params' parameter of the JSON web API.

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 · moderate confidence

FortiOS 5.4.0 through 5.4.5 contains a DoS vulnerability in the web GUI's JSON API where an authenticated attacker can send a specially crafted payload to the 'params' parameter, causing temporary GUI unresponsiveness.

MitigationUpgrade FortiOS to a version beyond 5.4.5 where the vulnerability is patched; if immediate upgrade is not feasible, restrict administrative access to trusted users and monitor for anomalous API requests.

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
FortiosOperating system
Affected:= 5.4.0= 5.4.1= 5.4.2= 5.4.3= 5.4.4= 5.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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. Verify FortiOS version
    Run 'get system status' via CLI or check the web GUI dashboard to confirm the installed FortiOS version number
    Affected if The version is 5.4.0, 5.4.1, 5.4.2, 5.4.3, 5.4.4, or 5.4.5
  2. Confirm web GUI is enabled
    Run 'get system interface' or check GUI settings via CLI to verify the web GUI service is enabled on management interfaces
    Affected if Web GUI is enabled on any accessible interface and the FortiOS version falls within the affected range
  3. Check for GUI JSON API access
    Review the administrative access settings with 'show system interface' or GUI access configuration to determine if HTTPS/HTTP API access is permitted
    Affected if Unrestricted or overly permissive administrative/API access is configured and FortiOS version is affected
  4. Examine logs for GUI DoS symptoms
    Search FortiOS event logs for entries indicating GUI unresponsiveness, timeout errors, or abnormal JSON API request patterns around the 'params' parameter
    Affected if Logs show recurring GUI hangs or API timeouts correlating with JSON API requests, and the version is within the affected range

You are affected if FortiOS version is 5.4.0 through 5.4.5 and the web GUI JSON API is accessible to authenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FortiOS to a version beyond 5.4.5 where the vulnerability is patched; if immediate upgrade is not feasible, restrict administrative access to trusted users and monitor for anomalous API requests.

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14182 — 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-2017-14182 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