dbcve.org
FortiproxyApplication · Fortinet

CVE-2022-42472

MEDIUM · 5.4 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to after 7.0.8 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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
A improper neutralization of crlf sequences in http headers ('http response splitting') in Fortinet FortiOS versions 7.2.0 through 7.2.2, 7.0.0 through 7.0.8, 6.4.0 through 6.4.11, 6.2.0 through 6.2.12, 6.0.0 through 6.0.16, FortiProxy 7.2.0 through 7.2.1, 7.0.0 through 7.0.7, 2.0.0 through 2.0.10, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6 may allow an authenticated and remote attacker to perform an HTTP request splitting attack which gives attackers control of the remaining headers and body of the response.

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

A detailed technical summary for this CVE is being prepared.

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:>= 1.1.0, <= 1.1.6>= 1.2.0, <= 1.2.13>= 2.0.0, <= 2.0.10>= 7.0.0, <= 7.0.7= 7.2.0= 7.2.1
FortiosOperating system
Affected:>= 6.0.1, <= 6.0.16>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.8= 7.2.0= 7.2.1= 7.2.2

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

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

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 7.0.8
Vendor patch fortiguard.com →
Recommended fix High confidence

FortiOS: upgrade to 7.0.9+, 6.4.12+, 6.2.13+, 6.0.17+, or 7.2.3+ (depending on your branch) | FortiProxy: upgrade to 7.0.8+, 2.0.11+, 1.2.14+, 1.1.7+, or 7.2.2+ (depending on your branch)

  1. 1. Identify the currently installed FortiOS or FortiProxy version from the device dashboard or via CLI command: 'get system status'
  2. 2. Determine which branch (6.0, 6.2, 6.4, 7.0, or 7.2) your current version belongs to
  3. 3. Access FortiGuard PSIRT FG-IR-22-362 at https://fortiguard.com/psirt/FG-IR-22-362 to obtain the official patch and upgrade guidance
  4. 4. Download the appropriate firmware upgrade from the Fortinet support portal: https://support.fortinet.com/
  5. 5. Upload the firmware to the Fortinet device via GUI (System > Firmware) or CLI: 'execute firmware upload'
  6. 6. Back up the current configuration before upgrading
  7. 7. Schedule a maintenance window as upgrades may cause brief service interruption
  8. 8. Perform the firmware upgrade and verify the device reboots successfully
Caveat Review release notes for your target version as minor firmware upgrades may include configuration changes; ensure compatibility with existing FortiGate policies and integrations

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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