FortiosOperating system · Fortinet
CVE-2018-13365
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 Exposure vulnerability in Fortinet FortiOS 6.0.1, 5.6.5 and below, allow attackers to learn private IP as well as the hostname of FortiGate via Application Control Block page.
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 confidenceFortiOS contains an information exposure vulnerability in the Application Control Block page. Unauthenticated or unauthorized attackers can access this page to retrieve private IP addresses and hostnames of FortiGate appliances. This is a classic information disclosure issue where sensitive network configuration details are exposed to unauthorized users.
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.6.5>= 5.6.6, <= 6.0.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 FortiOS versionRun 'get system status' or ' FortiOS -v' command via CLI to display the installed firmware version.Affected if The displayed version is 5.6.5 or earlier, OR is 5.6.6 through 6.0.1 inclusive.
-
Verify Application Control is enabledRun 'get system global | grep app' or check the Application Control configuration via 'show system interface' and review whether application control signatures are loaded.Affected if Application Control feature is enabled and application control profiles are applied to firewall policies.
-
Check Application Control Block page accessibilityAttempt to access the URL '/p/appctrl/block' or navigate to the Application Control Block interface through the web UI without authentication.Affected if The page is accessible without authentication or without proper admin privilege verification.
-
Review administrative access settingsRun 'get system interface' or check the 'set trust-ip-1' and administrative access settings in the system interface configuration.Affected if Administrative access (HTTP/HTTPS/SSH) is allowed from untrusted or any IP addresses.
You are affected if your FortiOS version falls within 5.6.5 or earlier, or 5.6.6 through 6.0.1, AND the Application Control Block interface is accessible to unauthorized or unauthenticated users.
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 6.0.2 or 5.6.6 or later to patch this vulnerability. As an interim measure, restrict access to the Application Control Block interface to trusted administrative networks only.
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-2018-13365 — 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-13365 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