Skip to content
Server Security Center
KEVmedium4.3 Used in ransomware campaigns

CVE-2018-13383: Fortinet FortiOS and FortiProxy Out-of-bounds Write

Fortinet FortiOS and FortiProxy · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-10.

CVSS v3.1 (CVE record)
4.3
medium
EPSS (exploit probability, 30 days)
31%
higher than 98.2% of all CVEs
Added to CISA KEV
2022-01-10
US federal due date 2022-07-10
Automatable (CISA SSVC)
no
technical impact: partial

What is CVE-2018-13383?

A heap buffer overflow in Fortinet FortiOS 6.0.0 through 6.0.4, 5.6.0 through 5.6.10, 5.4.0 through 5.4.12, 5.2.14 and earlier and FortiProxy 2.0.0, 1.2.8 and earlier in the SSL VPN web portal may cause the SSL VPN web service termination for logged in users due to a failure to properly handle javascript href data when proxying webpages.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Fortinet FortiOS and FortiProxy
    Affected
    • FortiProxy 2.0.0
    • FortiOS 6.0.0 through 6.0.4
    • 5.6.0 through 5.6.10
    • 5.4.0 through 5.4.12
    • 5.2.14 and earlier
    • 1.2.8 and earlier
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: fortiguard.com/advisory/FG-IR-18-388
  • CISA's deadline for US federal agencies: 2022-07-10 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-787 Out-of-bounds Write

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.