dbcve.org
FortiosOperating system · Fortinet

CVE-2017-14190

MEDIUM · 6.1 CVSS v3.0 Published 2018-01-29
Fix available
A fix is available. Upgrade to after 5.6.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Cross-site Scripting vulnerability in Fortinet FortiOS 5.6.0 to 5.6.2, 5.4.0 to 5.4.7, 5.2 and earlier, allows attacker to inject arbitrary web script or HTML via maliciously crafted "Host" header in user 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

A stored Cross-site Scripting vulnerability in Fortinet FortiOS allows attackers to inject arbitrary HTML or JavaScript via maliciously crafted Host headers in HTTP requests. The vulnerability affects versions 5.6.0-5.6.2, 5.4.0-5.4.7, and 5.2 and earlier.

MitigationUpgrade FortiOS to version 5.6.3, 5.4.8, or later which contains the patch. Alternatively, implement HTTP header validation or WAF rules at upstream devices to sanitize or block malicious Host headers.

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.2.0>= 5.4.0, <= 5.4.7>= 5.6.0, <= 5.6.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 FortiOS version
    Log into the FortiGate CLI and run the command 'get system status' or 'get system version' to retrieve the installed FortiOS version number
    Affected if The displayed version falls within 5.2.x and earlier, 5.4.0-5.4.7, or 5.6.0-5.6.2
  2. Verify firmware branch
    From the FortiOS CLI, run 'get system firmware' to see the full firmware version details including build number
    Affected if The firmware version matches any of the affected ranges listed in the CVE
  3. Cross-reference with official Fortinet advisory
    Visit the Fortinet security advisory page for CVE-2017-14190 and confirm your exact version is listed as vulnerable
    Affected if Your FortiOS version appears on the affected versions list and has not been patched to 5.6.3, 5.4.8, or later

If the FortiOS version is 5.6.2 or lower in the 5.6 branch, 5.4.7 or lower in the 5.4 branch, or 5.2.x or earlier, the system is vulnerable to stored XSS via malicious Host headers.

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
Upgrade available Upgrade to a release after 5.6.2
Interim mitigation

Upgrade FortiOS to version 5.6.3, 5.4.8, or later which contains the patch. Alternatively, implement HTTP header validation or WAF rules at upstream devices to sanitize or block malicious Host headers.

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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