dbcve.org
FortiproxyApplication · Fortinet

CVE-2024-55599

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 7.2.11 / 7.4.8 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 Improperly Implemented Security Check for Standard vulnerability [CWE-358] in FortiOS version 7.6.0, version 7.4.7 and below, 7.0 all versions, 6.4 all versions and FortiProxy version 7.6.1 and below, version 7.4.8 and below, 7.2 all versions, 7.0 all versions may allow a remote unauthenticated user to bypass the DNS filter via Apple devices.

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

This is a security bypass vulnerability (CWE-358) in FortiOS and FortiProxy where the DNS filter can be bypassed via Apple devices. An unauthenticated remote attacker can exploit this improperly implemented security check to circumvent DNS filtering protections.

MitigationUpdate FortiOS to version 7.4.8 or above (or 7.6.1+), and FortiProxy to version 7.4.9 or above (or 7.6.2+) to remediate this vulnerability. For immediate risk reduction, consider network segmentation or additional DNS filtering layers.

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
FortiproxyApplication
Affected:>= 7.0.0, < 7.4.9>= 7.6.0, < 7.6.2
FortisaseApplication
Affected:= 24.4.32
FortiosOperating system
Affected:>= 6.4.0, < 7.2.11>= 7.4.0, < 7.4.8= 7.6.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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check FortiOS version
    Run 'get system status' or 'show system status' in the FortiOS CLI to retrieve the firmware version
    Affected if The version is >= 6.4.0 and < 7.2.11, OR >= 7.4.0 and < 7.4.8, OR equals 7.6.0
  2. Check FortiProxy version
    Run 'get system status' or 'show system status' in the FortiProxy CLI to retrieve the firmware version
    Affected if The version is >= 7.0.0 and < 7.4.9, OR >= 7.6.0 and < 7.6.2
  3. Check FortiSASE version
    Run 'get system status' or query the FortiSASE admin portal for the current firmware version
    Affected if The version equals 24.4.32
  4. Verify DNS filter is enabled
    Run 'get dnsfilter profile' or 'show dnsfilter' in the CLI to check if any DNS filtering profiles are configured and applied to policy
    Affected if DNS filtering profiles exist and are actively applied to traffic policies

You are affected if your device runs an affected FortiOS, FortiProxy, or FortiSASE version AND DNS filtering is configured and active.

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.2.11 / 7.4.8 / 7.4.9 or later
Fixed in 7.2.117.4.87.4.9
Interim mitigation

Update FortiOS to version 7.4.8 or above (or 7.6.1+), and FortiProxy to version 7.4.9 or above (or 7.6.2+) to remediate this vulnerability. For immediate risk reduction, consider network segmentation or additional DNS filtering layers.

Recommended fix High confidence

FortiOS: 7.2.11+, 7.4.8+, or 7.6.1+ | FortiProxy: 7.4.9+ or 7.6.2+ | FortiSASE: any version > 24.4.32

  1. 1. Identify the Fortinet product (FortiOS, FortiProxy, or FortiSASE) currently deployed
  2. 2. Determine the exact current version from the affected version ranges provided
  3. 3. For FortiOS: Upgrade to version 7.2.11 or later, 7.4.8 or later, or 7.6.1 or later depending on your current branch
  4. 4. For FortiProxy: Upgrade to version 7.4.9 or later, or 7.6.2 or later depending on your current branch
  5. 5. For FortiSASE: Upgrade from version 24.4.32 to a later patched version
  6. 6. After upgrade, verify the DNS filter bypass is no longer reproducible on Apple devices
  7. 7. Review FortiOS/FortiProxy release notes for any additional security fixes included
Caveat Major version upgrades (e.g., 6.4 to 7.0, 7.0 to 7.4) may introduce configuration changes; review upgrade path and test in staging first

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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