Forticlient Endpoint Management ServerApplication · Fortinet

CVE-2021-44172

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to after 7.0.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 exposure of sensitive information to an unauthorized actor vulnerability [CWE-200] in FortiClientEMS versions 7.0.0 through 7.0.4, 7.0.6 through 7.0.7, in all 6.4 and 6.2 version management interface may allow an unauthenticated attacker to gain information on environment variables such as the EMS installation path.

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

FortiClientEMS management interface versions 7.0.0-7.0.4, 7.0.6-7.0.7, and all 6.4.x and 6.2.x contains an information disclosure vulnerability where an unauthenticated attacker can query environment variables including the EMS installation path through the management interface.

MitigationUpgrade FortiClientEMS to a fixed version beyond the affected ranges (7.0.7 for 7.x, or latest patched 6.4.x/6.2.x). Restrict network access to the management interface to trusted networks as a compensating control.

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
Forticlient Endpoint Management ServerApplication
Affected:>= 6.2.0, <= 6.2.9>= 6.4.0, <= 6.4.9>= 7.0.0, <= 7.0.4>= 7.0.6, <= 7.0.7

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Identify FortiClientEMS installation
    Check for the FortiClientEMS service on the Windows server. Open Services console (services.msc) and look for 'FortiClient Endpoint Management Server' or check Program Files for FortiClientEMS installation directory.
    Affected if FortiClientEMS service or installation directory is found on the system
  2. Determine FortiClientEMS version
    Access the FortiClientEMS management console and navigate to the About page, or check the version in the installer file or release notes included with the installation.
    Affected if The installed version falls within 6.2.0-6.2.9, 6.4.0-6.4.9, 7.0.0-7.0.4, or 7.0.6-7.0.7
  3. Verify management interface accessibility
    Confirm that the FortiClientEMS management interface web portal (typically ports 80 or 443) is reachable on the network. Check firewall rules and bindings on the EMS server.
    Affected if The management interface is accessible from network segments beyond the local server
  4. Confirm vulnerability trigger condition
    The vulnerability allows unauthenticated querying of environment variables through the management interface. Test by accessing the interface without credentials and attempting to retrieve server environment variables or installation paths.
    Affected if Unauthenticated access to the management interface returns environment variable data including the EMS installation path

You are affected if FortiClientEMS version is 6.2.0-6.2.9, 6.4.0-6.4.9, 7.0.0-7.0.4, or 7.0.6-7.0.7 AND the management interface is network-accessible.

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.

From vendor data
Upgrade available Upgrade to a release after 7.0.7
Interim mitigation

Upgrade FortiClientEMS to a fixed version beyond the affected ranges (7.0.7 for 7.x, or latest patched 6.4.x/6.2.x). Restrict network access to the management interface to trusted networks as a compensating control.

Fix this in Forticlient Endpoint Management Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2021-44172 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