dbcve.org
FortiedrApplication · Fortinet

CVE-2022-39949

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-02
Fix available
A fix is available. Upgrade to after 5.2.0.2288 or later.
See remediation →
57/100
Remediation priority · Elevated
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 improper control of a resource through its lifetime vulnerability [CWE-664] in FortiEDR CollectorWindows 4.0.0 through 4.1, 5.0.0 through 5.0.3.751, 5.1.0 may allow a privileged user to terminate the FortiEDR processes with special tools and bypass the EDR protection.

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 · moderate confidence

FortiEDR Collector for Windows contains an improper control of resource lifetime (CWE-664) that allows a privileged user to terminate FortiEDR processes using special tools, effectively bypassing the EDR protection. This is a local attack requiring existing privileged access.

MitigationUpgrade to Fortinet patched version (contact Fortinet for specific fixed releases) and restrict administrative privileges where possible to limit users who can terminate processes.

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
FortiedrApplication
Affected:>= 4.0.0, <= 4.1.0>= 5.0.0, <= 5.0.3.751>= 5.1.0, <= 5.2.0.2288

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 FortiEDR Collector is installed
    Open Windows Services (services.msc) or check Programs and Features for entries named 'FortiEDR' or 'Fortinet FortiEDR Collector'
    Affected if FortiEDR Collector is not found on the system, then this CVE does not apply
  2. Identify the FortiEDR Collector service
    In Windows Services, look for a service with 'FortiEDR' in the name (typically 'FortiEDR Collector' or similar) and note the service display name and status
    Affected if No FortiEDR-related service exists on the system
  3. Determine the installed FortiEDR Collector version
    Open Command Prompt or PowerShell and run: wmic product where "name like '%FortiEDR%'" get version, name OR check the executable file version in the FortiEDR installation directory (commonly in Program Files or Program Files x86)
    Affected if Cannot determine version - the system may still be vulnerable if FortiEDR is installed but version cannot be retrieved
  4. Compare installed version against affected ranges
    Check if the installed version falls within: 4.0.0 through 4.1.0, OR 5.0.0 through 5.0.3.751, OR 5.1.0 through 5.2.0.2288
    Affected if The installed version matches any of these three ranges, the system is affected by this vulnerability

The system is affected only if FortiEDR Collector for Windows is installed AND its version falls within one of the three affected version ranges (4.0.0-4.1.0, 5.0.0-5.0.3.751, or 5.1.0-5.2.0.2288).

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 a release after 5.2.0.2288
Interim mitigation

Upgrade to Fortinet patched version (contact Fortinet for specific fixed releases) and restrict administrative privileges where possible to limit users who can terminate processes.

Recommended fix Moderate confidence

FortiEDR 4.1.1+ (for 4.x), 5.0.4+ (for 5.0.x), or 5.3.0+ (for 5.1.x/5.2.x)

  1. 1. Identify the currently installed FortiEDR Collector version from the affected list (4.0.0-4.1.0, 5.0.0-5.0.3.751, or 5.1.0-5.2.0.2288)
  2. 2. Download the appropriate fixed version from Fortinet's FortiEDR support portal at fortinet.com/support or through your FortiCare contract
  3. 3. Upgrade FortiEDR Collector for Windows to version 4.1.1 or later (for 4.x branch), 5.0.4 or later (for 5.0.x branch), or 5.3.0 or later (for 5.1.x/5.2.x branch)
  4. 4. Verify the upgrade was successful by checking the FortiEDR Collector version in the FortiEDR console
  5. 5. Confirm that FortiEDR processes are running and protection is active
Caveat Review FortiEDR release notes for any compatibility changes before upgrading; ensure the upgrade is tested in a staging environment first

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

Fix this in Fortiedr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39949 — 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-2022-39949 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