FortiosOperating system · Fortinet
CVE-2017-3130
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 information disclosure vulnerability in Fortinet FortiOS 5.6.0, 5.4.4 and below versions allows attacker to get FortiOS version info by inspecting FortiOS IKE VendorID packets.
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 confidenceFortiOS exposes version information through IKE VendorID packets during VPN handshake negotiations. An attacker can passively inspect these packets to determine the exact FortiOS version, enabling targeted attacks against known vulnerabilities in that version.
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.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.0.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed FortiOS versionLog into the FortiGate CLI and run 'get system status' or check the FortiGate web UI under Dashboard > Status to view the current FortiOS firmware version.Affected if The version displayed is 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, or 5.0.11.
-
Determine if IPsec VPN is configuredIn FortiGate CLI, run 'show vpn ipsec phase1' to list active IPsec VPN phase-1 configurations. In the web UI, navigate to VPN > IPsec Wizard or VPN > IPsec to see configured tunnels.Affected if Any IPsec VPN phase-1 interface is configured and active, as this enables IKE negotiations where VendorID is transmitted.
-
Confirm IKE is enabled on the deviceIn FortiGate CLI, run 'config vpn ipsec phase1' then 'show' to display all phase1 configurations. Verify the 'ike' or 'ipsec' protocol settings are enabled.Affected if IKE version 1 or 2 is enabled in any VPN phase-1 configuration, which triggers the VendorID exchange during handshake.
-
Review VPN handshake from external perspectiveCapture IKE packets during VPN initiation from an external test system using a packet sniffer (such as Wireshark) or use 'diag vpn ike log' in FortiGate CLI to view IKE negotiation logs.Affected if The IKE VendorID payload in captured packets contains the specific FortiOS version string, exposing the exact firmware version to observers.
You are affected if your FortiOS version is 5.0.0 through 5.0.11 and you have any IPsec/IKE VPN tunnel configured, because the version is disclosed in IKE VendorID packets during VPN handshakes.
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 FortiOS to versions beyond 5.6.0 and 5.4.4, or apply vendor-supplied patches. Consider disabling IKE VendorID information disclosure if supported by configuration.
Fix this in Fortios
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3130 — 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-3130 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