FortiosOperating system · Fortinet
CVE-2017-3127
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 · uneditedA Cross-Site Scripting vulnerability in Fortinet FortiGate 5.2.0 through 5.2.10 allows attacker to execute unauthorized code or commands via the srcintf parameter during Firewall Policy Creation.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability in Fortinet FortiGate firewall versions 5.2.0 through 5.2.10 allows attackers to inject malicious scripts via the 'srcintf' parameter during Firewall Policy Creation. The vulnerability stems from insufficient input sanitization in the web management interface, enabling unauthorized code execution in the context of an authenticated administrator's session.
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
= 5.2.0= 5.2.1= 5.2.2= 5.2.3= 5.2.4= 5.2.5= 5.2.6= 5.2.7= 5.2.8= 5.2.9= 5.2.10CVSS 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.
-
Check FortiOS firmware versionRun the command 'get system status' via FortiGate CLI or check the web UI login page version display. Locate the 'FortiOS' or 'Firmware Version' field.Affected if The version displayed is 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2.5, 5.2.6, 5.2.7, 5.2.8, 5.2.9, or 5.2.10.
-
Confirm web management interface is enabledRun 'get system interface | grep -i admin' or check System > Interface settings in the web UI to verify HTTPS administrative access is enabled on any interface.Affected if The web UI (HTTPS) administrative access is enabled on one or more interfaces.
-
Identify exposed management interfacesRun 'show system interface' or view Network > Interfaces in the web UI to list all interfaces and their administrative access settings.Affected if Any interface has HTTPS administrative access enabled and is reachable from untrusted networks.
-
Verify firewall policy creation accessLog into the web UI as an administrator and navigate to Policy & Objects > Policy > IPv4. Confirm the ability to create a new firewall policy.Affected if You can access the firewall policy creation screen and the 'srcintf' parameter field is present.
You are affected if your FortiGate runs FortiOS version 5.2.0 through 5.2.10 AND the web management interface is accessible for authenticated administrators to create firewall policies.
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 FortiGate firmware to version 5.2.11 or later (or 5.4.x/5.6.x) to patch the vulnerability. As a temporary workaround, restrict administrative access to trusted IP addresses and minimize user interaction with the firewall policy creation interface.
Fix this in Fortios
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3127 — 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-3127 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