Fortinet released security advisories addressing vulnerabilities in FortiClient and FortiGate where an attacker could leverage some of these vulnerabilities to take control of an affected system.

In one issue with FortiGate, there is a heap-based buffer overflow flaw found in the SOCKS5 proxy handshake in the Curl package.

If Curl is unable to resolve the address itself, it passes the hostname to the SOCKS5 proxy. However, the maximum length of the hostname that can be passed is 255 bytes. If the hostname is longer, then Curl switches to the local name resolving and passes the resolved address only to the proxy.

The local variable that instructs Curl to “let the host resolve the name” could obtain the wrong value during a slow SOCKS5 handshake, resulting in the too-long hostname being copied to the target buffer instead of the resolved address, which was not the intended behavior.

CVE-2023-38545 is the case number for the vulnerability, which has a CVSS v3 base score of 8.1.

Schneider Bold

In additon, there is another vulnerability, CVE-2023-38546, with a low severity that affects libcurl only, not the tool.

A flaw was found in the Curl package which allows an attacker to insert cookies into a running program using libcurl if the specific series of conditions are met.

The following products suffer from the issues:

  • FortiGate (Only FGT_VM64_KVM model is impacted and authentication is required)
  • FGT_VM64_KVM version 7.4.0 through 7.4.1
  • FGT_VM64_KVM version 7.2.0 through 7.2.6
  • FGT_VM64_KVM version 7.0.1 through 7.0.13

In terms of a mitigation:

Upgrade to upcoming FGT_VM64_KVM version 7.4.2 or above

Upgrade to upcoming FGT_VM64_KVM version 7.2.7 or above

Click here for additional fixes for FortiClient vulnerabilities:

  • FG-IR-22-299: FortiClient (Windows) – Arbitrary file deletion from unprivileged users
  • FG-IR-23-274: FortiClient (Windows) – DLL Hijacking via openssl.cnf

Pin It on Pinterest

Share This