FortiportalApplication · Fortinet

CVE-2017-7338

HIGH · 7.5 CVSS v3.0 Published 2017-05-27
Fix available
A fix is available. Upgrade to after 4.0.0 or later.
See remediation →
84/100
Remediation priority · High
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
A password management vulnerability in Fortinet FortiPortal versions 4.0.0 and below allows an attacker to carry out information disclosure via the FortiAnalyzer Management View.

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

This is a password management vulnerability in Fortinet FortiPortal (versions 4.0.0 and below) that allows an attacker to obtain sensitive information through the FortiAnalyzer Management View, likely due to improper access controls or password exposure in the management interface.

MitigationUpgrade FortiPortal to a version newer than 4.0.0, or implement proper access controls and review FortiAnalyzer Management View configurations to ensure passwords and sensitive data are not exposed to unauthorized users.

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
FortiportalApplication
Affected:<= 4.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 FortiPortal installed version
    Access the FortiPortal admin interface and navigate to System > Settings > About, or check the version displayed on the login page. Alternatively, check the release notes or installation files used during deployment.
    Affected if The installed version is 4.0.0 or any version below 4.0.0.
  2. Locate FortiAnalyzer Management View configuration
    In the FortiPortal admin interface, navigate to the FortiAnalyzer or Management View section. This may be found under System Settings, Configuration, or a dedicated FortiAnalyzer menu item depending on the interface layout.
    Affected if The FortiAnalyzer Management View feature is present and accessible in the interface.
  3. Verify access controls on FortiAnalyzer Management View
    Examine the user roles, permissions, and access control lists associated with the FortiAnalyzer Management View. Check which user accounts or roles can access this view and whether low-privilege or unauthorized users can reach it.
    Affected if Users without administrative privileges or users outside the expected scope can access the FortiAnalyzer Management View.
  4. Inspect for exposed sensitive data in Management View
    Open the FortiAnalyzer Management View and visually inspect whether passwords, credentials, or other sensitive information are displayed in plain text or within exportable fields.
    Affected if Passwords, API keys, or other sensitive data are visible to users accessing the FortiAnalyzer Management View.

You are affected if your FortiPortal installation is version 4.0.0 or below and the FortiAnalyzer Management View is enabled, with sensitive data potentially exposed to unauthorized 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
Upgrade available Upgrade to a release after 4.0.0
Interim mitigation

Upgrade FortiPortal to a version newer than 4.0.0, or implement proper access controls and review FortiAnalyzer Management View configurations to ensure passwords and sensitive data are not exposed to unauthorized users.

Fix this in Fortiportal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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