Fortianalyzer FirmwareOperating system · Fortinet
CVE-2017-3126
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 FortiAnalyzer 5.4.0 through 5.4.2 and FortiManager 5.4.0 through 5.4.2 allows attacker to execute unauthorized code or commands via the next parameter.
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 confidenceOpen redirect vulnerability in FortiAnalyzer and FortiManager versions 5.4.0 through 5.4.2 allows attackers to manipulate the 'next' parameter to redirect users to malicious external sites. While the description mentions code/command execution, the CVSS 6.1 and 'open redirect' classification suggests the primary impact is phishing and credential theft via user redirection.
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
Fortianalyzer FirmwareOperating system
= 5.4.0= 5.4.1= 5.4.2
Fortimanager FirmwareOperating system
= 5.4.0= 5.4.1= 5.4.2CVSS 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 FortiAnalyzer firmware versionLog into the FortiAnalyzer CLI or GUI and navigate to System Settings > Dashboard > System Information, or run the command 'get system status' in the CLI to retrieve the firmware version.Affected if The version listed is 5.4.0, 5.4.1, or 5.4.2.
-
Identify FortiManager firmware versionLog into the FortiManager CLI or GUI and navigate to System Settings > Dashboard > System Information, or run the command 'get system status' in the CLI to retrieve the firmware version.Affected if The version listed is 5.4.0, 5.4.1, or 5.4.2.
-
Verify web login interface accessibilityAccess the FortiAnalyzer or FortiManager login page via HTTPS (typically port 443) using a browser. Observe if the login page loads successfully.Affected if The web interface is accessible and the device is running an affected version.
-
Test 'next' parameter for open redirect behaviorAfter reaching the login page, inspect the URL for a 'next' parameter. If present, modify the parameter value to an external domain such as 'https://example.com' and observe if the browser redirects to that external site after authentication or page load.Affected if The system redirects to the attacker-controlled URL specified in the 'next' parameter instead of validating or blocking it.
A system is affected if it runs FortiAnalyzer or FortiManager firmware version 5.4.0, 5.4.1, or 5.4.2 and the web interface responds to manipulation of the 'next' parameter by redirecting to an external domain.
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 FortiAnalyzer and FortiManager version 5.4.3 or later which contains the fix for this vulnerability. If immediate patching is not feasible, implement web application firewall rules to validate and sanitize redirect parameters.
Fix this in Fortianalyzer Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-3126 — 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-2017-3126 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