CVE-2018-13374: FortiGate & FortiADC - Read-only admins can obtain the LDAP credentials configured in the FortiGate and FortiADC using the LDAP test connectivity feature
A Improper Access Control in Fortinet FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4 allows attacker to obtain the LDAP server login credentials configured in FortiGate via pointing a LDAP server connectivity test request to a rogue LDAP server instead of the configured one.
Other sources
FortiGate's and FortiADC's read-only admins are able to point an LDAP server connectivity test request to a rogue LDAP server instead of the configured one, in order to obtain the LDAP server login credentials configured in the FortiGate.
— FortiGuard
Fortinet FortiOS and FortiADC contain an improper access control vulnerability that allows attackers to obtain the LDAP server login credentials configured in FortiGate by pointing a LDAP server connectivity test request to a rogue LDAP server.
— CISA
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
FortiOSto a version that resolves this vulnerability.Fixed in 6.0.2 - Upgrade
Upgrade
FortiADCto a version that resolves this vulnerability.Fixed in 6.0.1
Event History
Frequently Asked Questions
What is the severity of CVE-2018-13374?
CVE-2018-13374 has been classified as a high severity vulnerability due to improper access control allowing attackers to obtain sensitive LDAP server login credentials.
How do I fix CVE-2018-13374?
To mitigate CVE-2018-13374, upgrade FortiOS to version 6.0.3 or later, or any version above 5.6.7.
Which products are affected by CVE-2018-13374?
CVE-2018-13374 affects Fortinet FortiOS versions 5.6.7 and earlier, and versions 6.0.0 to 6.0.2, along with FortiADC versions 6.1.0, 6.0.0 to 6.0.1, and 5.4.0 to 5.4.4.
What type of attack does CVE-2018-13374 enable?
CVE-2018-13374 enables attackers to obtain sensitive LDAP server credentials by directing requests to a rogue LDAP server.
Is there a workaround for CVE-2018-13374?
Currently, the recommended action for CVE-2018-13374 is to update to the latest secure versions, as there are no effective workarounds.