dbcve.org
FortiproxyApplication · Fortinet

CVE-2024-54021

MEDIUM · 5.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.9 / 7.2.12 or later.
See remediation →
67/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 Improper Neutralization of CRLF Sequences in HTTP Headers ('http response splitting') vulnerability [CWE-113] in Fortinet FortiOS 7.2.0 through 7.6.0, FortiProxy 7.2.0 through 7.4.5 may allow a remote unauthenticated attacker to bypass the file filter via crafted HTTP headers.

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

HTTP Response Splitting (CRLF injection) vulnerability in FortiOS 7.2.0-7.6.0 and FortiProxy 7.2.0-7.4.5 allows remote unauthenticated attackers to inject CRLF sequences into HTTP headers, enabling bypass of file filtering controls through crafted HTTP header manipulation.

MitigationApply vendor-supplied patches (FortiOS 7.6.1 or later, FortiProxy 7.4.6 or later) from Fortinet support portal; verify file filter functionality post-patch.

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.2.0, < 7.2.12>= 7.4.0, < 7.4.6
FortiosOperating system
Affected:>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.5= 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
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify product type
    Run 'get system status' or check the system dashboard to determine if the device is running FortiOS or FortiProxy
    Affected if Device is FortiProxy or FortiOS
  2. Check FortiOS version
    Run 'get system status' or 'fortios -v' to retrieve the installed firmware version
    Affected if Version is 7.2.0-7.2.8, 7.4.0-7.4.4, or 7.6.0
  3. Check FortiProxy version
    Run 'get system status' or 'get system info' to retrieve the installed firmware version
    Affected if Version is 7.2.0-7.2.11 or 7.4.0-7.4.5
  4. Verify web proxy feature is enabled
    Run 'get proxy config' or check System > Feature Select > Proxy to see if the HTTP/HTTPS proxy is active
    Affected if Web proxy or HTTP inspection is enabled on the device
  5. Confirm file filter is configured
    Run 'get firewall profile-group' or check Security Profiles > File Filter to see if any file filtering profiles are applied
    Affected if File filtering profiles exist and are applied to proxy policies

The device is affected if it runs FortiOS 7.2.0-7.2.8, 7.4.0-7.4.4, or 7.6.0, or FortiProxy 7.2.0-7.2.11 or 7.4.0-7.4.5, and has the web proxy or HTTP inspection feature enabled with file filtering configured.

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.9 / 7.2.12 / 7.4.5 or later
Fixed in 7.2.97.2.127.4.5
Interim mitigation

Apply vendor-supplied patches (FortiOS 7.6.1 or later, FortiProxy 7.4.6 or later) from Fortinet support portal; verify file filter functionality post-patch.

Recommended fix High confidence

FortiOS: upgrade to 7.2.9, 7.4.5, or 7.6.1 or later | FortiProxy: upgrade to 7.2.12 or 7.4.6

  1. 1. Back up the current FortiOS or FortiProxy configuration via GUI (System > Maintenance > Backup) or CLI: 'execute backup config tftp <config_file> <tftp_server>'
  2. 2. Download the appropriate firmware upgrade from Fortinet Support Portal (https://support.fortinet.com)
  3. 3. For FortiOS: Navigate to System > Firmware > Upload or use CLI: 'execute upgrade firmware <image_file>'
  4. 4. For FortiProxy: Navigate to System > Firmware > Upgrade or use CLI: 'execute system firmware upgrade <image_file>'
  5. 5. Reboot the device and verify the upgrade completed successfully
  6. 6. Confirm the version matches the fixed release: FortiOS 7.2.9+, 7.4.5+, or 7.6.1+ / FortiProxy 7.2.12+ or 7.4.6+
  7. 7. Verify configuration integrity and test expected functionality
Caveat Review Fortinet release notes for minor version upgrade considerations; ensure compatibility with existing feature set

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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