FortianalyzerApplication · Fortinet
CVE-2018-1355
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 · uneditedAn open redirect vulnerability in Fortinet FortiManager 6.0.0, 5.6.5 and below versions, FortiAnalyzer 6.0.0, 5.6.5 and below versions allows attacker to inject script code during converting a HTML table to a PDF document under the FortiView feature. An attacker may be able to social engineer an authenticated user into generating a PDF file containing injected malicious URLs.
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 confidenceAn open redirect vulnerability exists in FortiManager and FortiAnalyzer where the FortiView feature's HTML table to PDF conversion does not properly sanitize injected script code/URLs. An authenticated attacker leverages social engineering to trick a user into generating a PDF document that contains malicious redirected URLs, potentially leading to phishing or further compromise.
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
FortianalyzerApplication
<= 5.6.5= 6.0.0
FortimanagerApplication
<= 5.6.5= 6.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed FortiManager or FortiAnalyzer versionAccess the product CLI or web interface and retrieve the current firmware version. In CLI, this is typically done with 'get system status' or checking the Dashboard in the web UI.Affected if The version is 5.6.5 or lower, or exactly 6.0.0, indicating it falls within the affected version ranges.
-
Verify FortiView feature is enabledCheck the system configuration or feature visibility settings to determine if FortiView module is available to users. In the web UI, this appears under the FortiView menu option.Affected if FortiView is accessible to authenticated users, as the vulnerability requires this feature to be available for exploitation.
-
Confirm PDF export capability exists for FortiViewNavigate to any FortiView summary page in the web interface and look for a PDF export or download button/icon that converts the displayed HTML table to PDF.Affected if PDF generation functionality is present and usable, as this is the specific vector through which the malicious redirect is delivered.
-
Check user authentication and privilege levelsReview which authenticated users have access to FortiView and its export functions. Low-privilege users with FortiView access could be exploited via social engineering.Affected if Authenticated users (even low-privilege) can access FortiView and trigger PDF generation, providing an attack surface for the vulnerability.
You are affected if your FortiManager or FortiAnalyzer version is 5.6.5 or lower, or exactly 6.0.0, AND the FortiView feature with PDF export is accessible to authenticated users in your environment.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to FortiManager and FortiAnalyzer versions 6.0.1/5.6.6 or later to obtain the patch. If upgrading is not immediately feasible, restrict or disable the FortiView PDF generation feature and educate users about social engineering tactics.
Fix this in Fortianalyzer
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1355 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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