FortiosOperating system · Fortinet
CVE-2014-0351
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 · uneditedThe FortiManager protocol service in Fortinet FortiOS before 4.3.16 and 5.x before 5.0.8 on FortiGate devices does not prevent use of anonymous ciphersuites, which makes it easier for man-in-the-middle attackers to obtain sensitive information or interfere with communications by modifying the client-server data stream.
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 confidenceThe FortiManager protocol service in Fortinet FortiOS before 4.3.16 and 5.0.8 fails to disable anonymous SSL/TLS ciphersuites (e.g., DH_anon, ECDH_anon), which provide no server authentication. This allows man-in-the-middle attackers to intercept or modify FortiGate management traffic by exploiting the unauthenticated encryption.
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
<= 4.3.15= 4.3.10= 4.3.12= 4.3.13= 4.3.14= 5.0.0= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:M/Au:N/C:P/I:P/A:P
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 versionRun 'get system status' or 'get system version' via CLI or check the web UI dashboard to identify the installed FortiOS versionAffected if Version is 4.3.15 or lower, or one of the specific affected versions 4.3.10/12/13/14, or 5.0.0/3/4/5/6/7
-
Verify FortiManager protocol service is enabledRun 'get fmpro status' or check Configuration > FortiManager in the web UI to see if the FortiManager protocol service is configuredAffected if FortiManager service is enabled and managing FortiGate devices
-
Inspect SSL/TLS cipher configuration for FortiManagerRun 'show fmprofile' or check the FortiManager profile settings for SSL/TLS cipher list. Look for presence of anonymous ciphers such as ADH, DH_anon, ECDH_anon, or 'aNULL' cipher suitesAffected if Anonymous/unauthenticated ciphers (DH_anon, ECDH_anon, ADH, or aNULL) are listed in the enabled cipher suite configuration
-
Review management traffic encryption settingsRun 'get system interface' or check the management interface SSL settings to verify encryption configuration used for FortiGate-FortiManager communicationAffected if The management interface is configured to allow unauthenticated cipher suites for SSL/TLS connections
User is affected if running FortiOS version 4.3.15 or below, or version 5.0.0 through 5.0.7, AND the FortiManager protocol service is enabled with anonymous SSL/TLS ciphers still permitted.
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 version 4.3.16 or later (for 4.x branches) or 5.0.8 or later (for 5.x branches) to receive the patch that disables anonymous ciphersuites in the FortiManager protocol service.
Fix this in Fortios
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0351 — 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-2014-0351 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