Safeguard
Vulnerability Analysis•

CVE-2020-12820: Medium Stack Overflow in FortiOS FortiClient NAC Daemon

CVE-2020-12820 is a medium stack overflow in the FortiOS FortiClient NAC daemon on non-default setups. Upgrade to FortiOS 5.6.13, 6.0.11 or later.

Safeguard Security Team
3 min read

CVE-2020-12820 is a medium severity (CVSS 5.4) stack buffer overflow in FortiOS under non-default configuration. An authenticated SSL VPN user can crash the FortiClient NAC daemon by requesting a large file name. FortiOS 6.0.10 and 5.6.12 and below are affected. Upgrade to 5.6.13 or 6.0.11 or later.

What's affected

  • FortiOS 6.0.10 and below, and 5.6.12 and below.
  • Fixed: 5.6.13 or later, and 6.0.11 or later. FortiOS 6.2.0 and later are not affected, per Fortinet.
  • Workaround: make sure FortiHeartbeat and Endpoint Compliance are not both enabled on the same interface.

The record scores it 5.4 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

Run get system status for the version, then check whether endpoint compliance and FortiHeartbeat are both enabled on any interface with show system interface.

What to do now

  1. Read the FortiOS version on every FortiGate.
  2. Upgrade 5.6 and 6.0 devices to the fixed builds.
  3. Check interfaces for the risky configuration combination.
  4. Disable endpoint compliance and FortiHeartbeat together on an interface if you cannot patch.
  5. Check logs for fcnacd crashes.

After you patch, record the new version for FortiOS FortiClient NAC in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps this to CWE-121, stack based buffer overflow, and CWE-787. A very long file name overruns a fixed buffer.

Fortinet says it is not aware of proof of concept code achieving code execution. The confirmed effect is a daemon crash, and the non-default configuration narrows who is exposed.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Quick check

Does it affect default setups?

No. The record says non-default configuration. Fortinet's workaround is to avoid enabling both FortiHeartbeat and Endpoint Compliance on one interface.

How do I find every place FortiOS FortiClient NAC is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.