dbcve.org
ForticlientApplication · Fortinet

CVE-2023-45590

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 7.0.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
An improper control of generation of code ('code injection') in Fortinet FortiClientLinux version 7.2.0, 7.0.6 through 7.0.10 and 7.0.3 through 7.0.4 allows attacker to execute unauthorized code or commands via tricking a FortiClientLinux user into visiting a malicious website

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 confidence

Code injection vulnerability in FortiClientLinux allows remote attackers to execute unauthorized code or commands by tricking users into visiting malicious websites. The vulnerability stems from improper control of code generation in affected versions (7.2.0, 7.0.6-7.0.10, 7.0.3-7.0.4).

MitigationApply vendor-supplied patches to update FortiClientLinux to a fixed version. Users should be trained to avoid visiting untrusted websites to reduce attack surface.

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
ForticlientApplication
Affected:>= 7.0.6, < 7.0.11= 7.0.3= 7.0.4= 7.2.0

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify FortiClientLinux installation
    Check if FortiClientLinux is present on the system by searching common installation directories (/opt, /Applications) or querying the package manager (dpkg -l | grep -i forti or rpm -qa | grep -i forticlient)
    Affected if FortiClientLinux is found installed on the system
  2. Retrieve installed FortiClientLinux version
    Run the FortiClientLinux binary with version flag (e.g., /opt/forticlient/forticlient --version) or query via package manager (dpkg -l forticlient or rpm -q forticlient)
    Affected if The command returns a version number that can be compared to affected ranges
  3. Compare version against affected ranges
    Check if the installed version matches 7.0.3, 7.0.4, or falls within 7.0.6 through 7.0.10 inclusive, or equals 7.2.0
    Affected if Installed version is 7.0.3, 7.0.4, 7.0.6-7.0.10, or 7.2.0
  4. Confirm FortiClientLinux feature is enabled
    Verify the FortiClientLinux application or any of its components (such as web protection, antivirus, or related modules) are actively running or enabled on the system
    Affected if FortiClientLinux with vulnerable components is running and the system processes web content or files through it

A user is affected if FortiClientLinux is installed with version 7.0.3, 7.0.4, 7.0.6-7.0.10, or 7.2.0 and the application or its features are actively in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0.11 or later
Fixed in 7.0.11
Interim mitigation

Apply vendor-supplied patches to update FortiClientLinux to a fixed version. Users should be trained to avoid visiting untrusted websites to reduce attack surface.

Recommended fix High confidence

FortiClientLinux 7.0.11 or later (or 7.2.x if newer branch)

  1. 1. Identify the current FortiClientLinux version installed by checking the software or using command line tools
  2. 2. If version is 7.0.3, 7.0.4, or 7.0.6 through 7.0.10, plan for upgrade
  3. 3. If version is 7.2.0, check for available 7.2.x updates from Fortinet
  4. 4. Download FortiClientLinux version 7.0.11 or later from Fortinet's official download portal
  5. 5. Uninstall the current FortiClientLinux version following Fortinet's documented removal procedure
  6. 6. Install the upgraded version (7.0.11 or later) using standard installation procedures
  7. 7. Verify the installation completed successfully and confirm the new version number
  8. 8. Test that FortiClientLinux functionality remains operational
Caveat Review Fortinet release notes for any functionality changes between current and new version; enterprise deployments should test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Forticlient Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45590 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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