FortisiemApplication · Fortinet
CVE-2018-13378
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 FortiSIEM 5.2.0 and below versions exposes the LDAP server plaintext password via the HTML source code.
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 confidenceFortiSIEM versions 5.2.0 and below expose the LDAP server plaintext password in the HTML source code of the web interface, allowing authenticated attackers to view sensitive authentication credentials via client-side inspection.
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
FortisiemApplication
<= 5.2.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 FortiSIEM versionLog into the FortiSIEM administrative interface or check the system information page. Alternatively, run the command 'phchk -v' or check the About section in the GUI to retrieve the installed version number.Affected if The installed version is 5.2.0 or any version lower than 5.2.0.
-
Confirm LDAP authentication is configuredNavigate to the FortiSIEM admin panel and inspect whether LDAP integration has been set up under the Users or Authentication settings. Look for configured LDAP servers.Affected if LDAP is configured and connected to an external directory service.
-
Inspect HTML source for exposed credentialsUsing an authenticated web browser session, log into the FortiSIEM web interface. Right-click anywhere on the page and select 'View Page Source' or use browser developer tools (F12) to examine the HTML. Search for patterns such as 'password', 'pwd', or the LDAP bind password string within the source code.Affected if A plaintext LDAP password appears in the HTML source code.
-
Check network traffic for credential leakageUse a proxy tool or browser developer tools to capture HTTP responses from the FortiSIEM web application. Examine responses for any JSON, HTML, or script content that contains LDAP credentials in cleartext.Affected if LDAP passwords are returned in plaintext within HTTP responses.
You are affected if FortiSIEM version is 5.2.0 or lower AND LDAP authentication is configured, with the password visible in client-side HTML or HTTP responses.
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 FortiSIEM to a version newer than 5.2.0 and rotate any LDAP credentials that may have been exposed.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13378 — 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-13378 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