dbcve.org
FortiisolatorWeb server / proxy · Fortinet

CVE-2024-27779

MEDIUM · 6.7 CVSS v3.1 Published 2025-07-18
Fix available
A fix is available. Upgrade to 2.4.5 / 4.2.7 or later.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable 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 insufficient session expiration vulnerability [CWE-613] in FortiSandbox FortiSandbox version 4.4.4 and below, version 4.2.6 and below, 4.0 all versions, 3.2 all versions and FortiIsolator version 2.4 and below, 2.3 all versions, 2.2 all versions, 2.1 all versions, 2.0 all versions, 1.2 all versions may allow a remote attacker in possession of an admin session cookie to keep using that admin's session even after the admin user was deleted.

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

This is a session management vulnerability where admin session cookies remain valid even after the associated admin user account is deleted from the system. An attacker who has obtained a valid admin session cookie can continue to authenticate and perform privileged actions on FortiSandbox or FortiIsolator even after the admin user has been removed.

MitigationImplement proper session invalidation that validates user existence on each session use and invalidates all sessions associated with a user upon account deletion.

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
FortiisolatorWeb server / proxy
Affected:>= 1.2.0, < 2.4.5
FortisandboxApplication
Affected:>= 3.2.0, < 4.2.7>= 4.4.0, < 4.4.5

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

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

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 the product name
    Determine whether the system is running FortiSandbox or FortiIsolator
    Affected if The product is FortiSandbox or FortiIsolator
  2. Check the installed version
    Use the product's version display command or admin web UI to determine the current firmware version
    Affected if The version is FortiIsolator >= 1.2.0 and < 2.4.5, or FortiSandbox >= 3.2.0 and < 4.2.7, or FortiSandbox >= 4.4.0 and < 4.4.5
  3. Review admin session behavior after user deletion
    Delete an admin user who has an active session and observe whether that session remains valid for authentication
    Affected if The deleted admin user's session cookie continues to authenticate successfully after the user account is removed

The environment is affected if running an affected version and active admin sessions persist after the associated admin user account is deleted.

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 2.4.5 / 4.2.7 / 4.4.5 or later
Fixed in 2.4.54.2.74.4.5
Interim mitigation

Implement proper session invalidation that validates user existence on each session use and invalidates all sessions associated with a user upon account deletion.

Recommended fix High confidence

FortiIsolator: upgrade to >= 2.4.5; FortiSandbox: upgrade to >= 4.2.7 (for 3.2/4.0/4.2 branches) or >= 4.4.5 (for 4.4 branch)

  1. 1. Identify the installed Fortinet product (FortiSandbox or FortiIsolator) and current version using the web UI or CLI.
  2. 2. For FortiIsolator: Plan upgrade to version 2.4.5 or later.
  3. 3. For FortiSandbox: If running version 3.2.x, 4.0.x, or 4.2.x, plan upgrade to version 4.2.7 or later. If running version 4.4.x, plan upgrade to version 4.4.5 or later.
  4. 4. Before upgrading, backup the current configuration through the FortiSandbox/FortiIsolator web UI or CLI.
  5. 5. Perform the upgrade following Fortinet's standard upgrade procedure for the specific appliance or VM version.
  6. 6. After upgrade, verify the new version is installed and the session expiration behavior is corrected.
  7. 7. As a security precaution after remediation, consider invalidating all existing admin sessions or forcing re-authentication.
Caveat Standard Fortinet appliance/VM upgrade considerations apply - review release notes for migration warnings, and test in a non-production environment first

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

Fix this in Fortiisolator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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