FortiosOperating system · Fortinet

CVE-2018-9185

HIGH · 8.1 CVSS v3.0 Published 2018-07-05
Fix available
A fix is available. Upgrade to after 6.0.0 or later.
See remediation →
90/100
Remediation priority · Urgent
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 information disclosure vulnerability in Fortinet FortiOS 6.0.0 and below versions reveals user's web portal login credentials in a Javascript file sent to client-side when pages bookmarked in web portal use the Single Sign-On feature.

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 6.0.0 and below contains an information disclosure vulnerability where web portal login credentials are exposed in a JavaScript file sent to the client-side when users bookmark pages that utilize the Single Sign-On feature.

MitigationUpgrade FortiOS to version 6.0.1 or later to remediate this vulnerability. Until the upgrade is applied, advise users to avoid bookmarking SSO-enabled web portal pages.

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:<= 6.0.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Identify FortiOS version
    Run 'get system status' or 'diagnose system version' command on the FortiGate device to retrieve the installed FortiOS version
    Affected if The displayed version is 6.0.0 or any version lower than 6.0.1
  2. Confirm web portal is configured
    Check for web portal configuration using 'get vpn ssl web portal' or review web portal settings in the FortiGate GUI under VPN > SSL-VPN Web Portal
    Affected if A web portal is configured and active on the device
  3. Verify Single Sign-On feature is enabled
    Examine the web portal configuration for SSO-related settings such as 'pre-authentication' or 'sso' in the portal settings. Check if the portal uses Windows AD or other SSO integration
    Affected if SSO is enabled within the web portal configuration
  4. Inspect for bookmarked SSO portal pages
    Review user bookmarked URLs for the SSL-VPN web portal. Look for URLs containing '/sslvpn/' or '/remote/saml?' patterns that indicate SSO-enabled access
    Affected if Users have created bookmarks pointing to SSO-enabled portal pages
  5. Examine client-side JavaScript for credential exposure
    When accessing a bookmarked SSO portal page, use browser developer tools to inspect the JavaScript files loaded. Search for login credentials, tokens, or authentication parameters embedded in client-side scripts
    Affected if Credentials or sensitive authentication data are visible in JavaScript files served to the client

A system is affected if it runs FortiOS 6.0.0 or below and has users who have bookmarked SSO-enabled web portal pages, resulting in credentials being exposed in client-side JavaScript.

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 6.0.0
Interim mitigation

Upgrade FortiOS to version 6.0.1 or later to remediate this vulnerability. Until the upgrade is applied, advise users to avoid bookmarking SSO-enabled web portal pages.

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-9185 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