FortiosOperating system · Fortinet
CVE-2018-13371
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 external control of system vulnerability in FortiOS may allow an authenticated, regular user to change the routing settings of the device via connecting to the ZebOS component.
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 confidenceThis is an authenticated privilege escalation vulnerability in FortiOS where a regular (non-privileged) user can manipulate routing settings through the ZebOS component, allowing external control of system routing configuration.
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.4.10>= 5.6.0, <= 5.6.7>= 6.0.0, <= 6.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 FortiOS versionRun the command 'get system status' on the FortiGate CLI to display the firmware versionAffected if The displayed version falls within <= 5.4.10, >= 5.6.0 through 5.6.7, or >= 6.0.0 through 6.0.2
-
Verify ZebOS routing access for regular usersReview user group configurations and admin profiles using 'show system admin' and 'show user group' to identify which users have access to routing-related functionalityAffected if Regular (non-privileged) user accounts or groups are granted permission to access ZebOS or routing configuration features
-
Inspect routing configuration for unauthorized changesRun 'get router info routing-table' and compare against known-good baselines or review configuration backups for unexpected static routes or routing policy changesAffected if Routing entries exist that were not intentionally configured by administrators with full privileges
-
Check admin profile privilegesRun 'show system admin' and review each administrator's profile to determine which profiles permit access to 'router' or 'routing' functionsAffected if Any admin profile assigned to non-privileged users includes router configuration permissions
You are affected if your FortiOS version is in the affected ranges AND regular users have access to ZebOS routing functionality without proper privilege restrictions.
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 dataApply the Fortinet patch for CVE-2018-13371 which restricts regular users from accessing ZebOS routing functionality. If immediate patching is not possible, audit user privileges and monitor for unauthorized routing changes.
Fix this in Fortios
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13371 — 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-13371 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