dbcve.org
FortiproxyApplication · Fortinet

CVE-2022-41329

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-07
Fix available
A fix is available. Upgrade to after 7.2.3 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 exposure of sensitive information to an unauthorized actor vulnerability [CWE-200] in Fortinet FortiProxy version 7.2.0 through 7.2.1 and 7.0.0 through 7.0.7, FortiOS version 7.2.0 through 7.2.3 and 7.0.0 through 7.0.9 allows an unauthenticated attackers to obtain sensitive logging informations on the device via crafted HTTP GET requests.

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

FortiProxy and FortiOS contain an information disclosure vulnerability (CWE-200) where unauthenticated attackers can obtain sensitive logging information via crafted HTTP GET requests. The vulnerability affects FortiProxy 7.2.0-7.2.1 and 7.0.0-7.0.7, as well as FortiOS 7.2.0-7.2.3 and 7.0.0-7.0.9.

MitigationUpgrade to FortiOS 7.2.4 or 7.0.10 or later, and FortiProxy 7.2.2 or later to remediate this vulnerability.

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.0.8>= 7.2.0, <= 7.2.2
FortiosOperating system
Affected:>= 6.2.3, <= 6.2.13>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.9>= 7.2.0, <= 7.2.3

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 and firmware version
    Log into the FortiProxy or FortiOS CLI and run the command: get system status or get system version
    Affected if The displayed firmware version falls within the affected ranges: FortiOS 6.2.3-6.2.13, 6.4.0-6.4.11, 7.0.0-7.0.9, 7.2.0-7.2.3 or FortiProxy 7.0.0-7.0.8, 7.2.0-7.2.2
  2. Verify HTTP management interface is exposed
    Check the management interface configuration by running: get system interface <interface_name> and look for 'set http 1' or check if port 80/443 is accessible from untrusted networks
    Affected if HTTP or HTTPS management is enabled and reachable from untrusted networks (WAN interface)
  3. Confirm logging is enabled
    Run the command: get log syslogd setting to check if logging to syslog is configured, and: get log memory setting to check memory logging status
    Affected if Syslog, memory logging, or other logging features are enabled, as the vulnerability exposes sensitive logging information

Your environment is affected if you are running a FortiOS or FortiProxy version within the affected ranges AND the HTTP management interface is exposed to untrusted networks, regardless of logging configuration status.

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 7.2.3
Interim mitigation

Upgrade to FortiOS 7.2.4 or 7.0.10 or later, and FortiProxy 7.2.2 or later to remediate this vulnerability.

Recommended fix Moderate confidence

FortiOS 7.0.10+ or 7.2.4+ | FortiProxy 7.0.9+ or 7.2.3+

  1. 1. Identify the current FortiOS or FortiProxy version by running: get system status
  2. 2. For FortiOS systems: If running 7.0.0-7.0.9, upgrade to FortiOS 7.0.10 or later; if running 7.2.0-7.2.3, upgrade to FortiOS 7.2.4 or later
  3. 3. For FortiProxy systems: If running 7.0.0-7.0.8, upgrade to FortiProxy 7.0.9 or later; if running 7.2.0-7.2.2, upgrade to FortiProxy 7.2.3 or later
  4. 4. Download the firmware from the Fortinet support portal (https://support.fortinet.com)
  5. 5. Upload and install the firmware via the FortiGate/FortiProxy web UI or CLI: execute restore image <tftp/ftp/scpc> <filename>
  6. 6. After reboot, verify the new version: get system status
  7. 7. Review new logging configurations to ensure sensitive information is properly protected
Caveat Review release notes for each major version jump; minor version upgrades typically have minimal breaking changes but review for deprecated features

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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