dbcve.org
FortiproxyApplication · Fortinet

CVE-2022-43947

HIGH · 8.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 6.4.13 / 7.0.8 or later.
See remediation →
94/100
Remediation priority · Urgent
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 improper restriction of excessive authentication attempts vulnerability [CWE-307] in Fortinet FortiOS version 7.2.0 through 7.2.3 and before 7.0.10, FortiProxy version 7.2.0 through 7.2.2 and before 7.0.8 administrative interface allows an attacker with a valid user account to perform brute-force attacks on other user accounts via injecting valid login sessions.

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

FortiOS and FortiProxy fail to properly restrict excessive authentication attempts, allowing an authenticated attacker with a valid user account to perform brute-force attacks on other user accounts by injecting valid login sessions. This bypasses account lockout or rate-limiting protections.

MitigationUpgrade to FortiOS 7.0.10/7.2.4+ or FortiProxy 7.0.8/7.2.3+ to patch the vulnerability, and review/adjust administrative account lockout policies and login attempt rate limiting.

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:>= 1.0.0, <= 2.0.9>= 7.0.0, < 7.0.8>= 7.2.0, < 7.2.2
FortiosOperating system
Affected:>= 6.2.0, < 6.4.13>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.4

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
High
Integrity
High
Availability
High

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

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 and version
    Run 'get system status' or 'get system info' via CLI to retrieve FortiOS or FortiProxy version and build number
    Affected if Product is FortiOS version 6.2.0 to 6.4.12, 7.0.0 to 7.0.10, or 7.2.0 to 7.2.3; OR FortiProxy version 1.0.0 to 2.0.9, 7.0.0 to 7.0.7, or 7.2.0 to 7.2.2
  2. Confirm admin or user authentication is enabled
    Check system global settings or policy configuration for authentication services (GUI: System > Settings > Authentication or CLI: 'show system global' and 'show user authentication')
    Affected if Local user authentication, RADIUS, or LDAP authentication is configured and enabled for administrative or user access
  3. Verify brute-force protection status
    Review account lockout settings via 'show system accprofile' or 'show user local' and check if 'block-enable' or account-lockout thresholds are configured
    Affected if Account lockout is not enforced or rate-limiting is disabled for login attempts
  4. Review authentication logs for session injection indicators
    Examine logs via 'execute log filter' and 'execute log display' for duplicate session IDs, concurrent sessions from same source, or authentication anomalies
    Affected if Logs show unusual session patterns, multiple authentication attempts bypassing lockout, or duplicate session tokens

Environment is affected if running an affected FortiOS or FortiProxy version with authentication enabled and without proper session injection controls or enforced account lockout policies.

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 6.4.13 / 7.0.8 / 7.0.11 or later
Fixed in 6.4.137.0.87.0.11
Interim mitigation

Upgrade to FortiOS 7.0.10/7.2.4+ or FortiProxy 7.0.8/7.2.3+ to patch the vulnerability, and review/adjust administrative account lockout policies and login attempt rate limiting.

Recommended fix High confidence

FortiOS: 6.4.13+, 7.0.11+, or 7.2.4+ | FortiProxy: 7.0.8+ or 7.2.2+

  1. 1. Identify the currently installed FortiOS or FortiProxy version by running 'get system status' or 'get system version' in the CLI
  2. 2. Based on your current major version branch, upgrade to the fixed release: For FortiOS 6.x branch, upgrade to 6.4.13 or later; For FortiOS 7.0.x branch, upgrade to 7.0.11 or later; For FortiOS 7.2.x branch, upgrade to 7.2.4 or later; For FortiProxy 7.0.x branch, upgrade to 7.0.8 or later; For FortiProxy 7.2.x branch, upgrade to 7.2.2 or later
  3. 3. Download the firmware from Fortinet's support portal (support.fortinet.com) after authenticating
  4. 4. Upload and install the firmware via the FortiOS/FortiProxy CLI using 'execute firmware upgrade' or via the web GUI under System > Firmware
  5. 5. After upgrade, verify the new version is installed with 'get system status'
  6. 6. Test that administrative access and user authentication functionality works correctly
Caveat Review Fortinet release notes for your specific upgrade path for any configuration or behavioral changes between your current version and the target version

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-2022-43947 — 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-43947 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