FortiapApplication · Fortinet
CVE-2022-29058
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 · uneditedAn improper neutralization of special elements [CWE-89] used in an OS command vulnerability [CWE-78] in the command line interpreter of FortiAP 6.0.0 through 6.4.7, 7.0.0 through 7.0.3, 7.2.0, FortiAP-S 6.0.0 through 6.4.7, FortiAP-W2 6.0.0 through 6.4.7, 7.0.0 through 7.0.3, 7.2.0 and FortiAP-U 5.4.0 through 6.2.3 may allow an authenticated attacker to execute unauthorized commands via specifically crafted arguments to existing commands.
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 confidenceA command injection vulnerability exists in the FortiAP command line interpreter where authenticated attackers can execute unauthorized OS commands via crafted arguments to existing commands. This vulnerability combines CWE-89 (SQL injection) and CWE-78 (OS command injection), allowing privilege escalation through the CLI interface.
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
FortiapApplication
>= 6.0.0, <= 6.0.6>= 6.4.3, < 6.4.8>= 7.0.0, < 7.0.4= 7.2.0
Fortiap SApplication
>= 6.0.0, <= 6.0.6>= 6.2.0, <= 6.2.6>= 6.4.0, < 6.4.8
Fortiap UApplication
>= 5.4.0, <= 5.4.6>= 6.0.0, <= 6.0.4>= 6.2.0, < 6.2.4
Fortiap W2Application
>= 6.0.0, <= 6.0.6>= 6.2.0, <= 6.2.6>= 6.4.0, < 6.4.8>= 7.0.0, < 7.0.4= 7.2.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiAP model and firmware versionAccess the FortiAP CLI and run the command: 'get system status' or use FortiManager/FortiCloud to query the device firmware version. Alternatively, check the FortiAP web UI dashboard for the firmware version displayed.Affected if The displayed firmware version falls within any of these ranges: FortiAP 6.0.0-6.0.6, 6.4.3-6.4.7, 7.0.0-7.0.3, or 7.2.0; FortiAP S 6.0.0-6.0.6, 6.2.0-6.2.6, or 6.4.0-6.4.7; FortiAP U 5.4.0-5.4.6, 6.0.0-6.0.4, or 6.2.0-6.2.3; FortiAP W2 6.0.0-6.0.6, 6.2.0-6.2.6, 6.4.0-6.4.7, 7.0.0-7.0.3, or 7.2.0.
-
Confirm CLI interface is accessibleVerify that the FortiAP CLI interface is enabled and reachable. Check via FortiGate managed AP configuration: 'config wireless-controller vap' and verify the enable-cli-local-profiling setting, or confirm SSH/Telnet access to the FortiAP device is permitted.Affected if CLI access is enabled and reachable from an untrusted network segment, as the vulnerability is exploited through authenticated CLI commands.
-
Review CLI user access logs for suspicious commandsExamine FortiAP or FortiGate controller logs for any unexpected or unauthorized CLI command execution. Use 'execute log filter' and 'execute log display' to review historical CLI activity, or check FortiGate wireless controller logs for managed AP command events.Affected if Logs contain CLI commands that are unexpected, malformed, or contain shell metacharacters (such as ; | & $ or backticks) that may indicate command injection attempts.
-
Check for unauthorized local administrator accountsFrom the FortiAP CLI, run 'get system admin' to list local administrator accounts. Compare against known, expected admin accounts. Also check FortiGate controller for managed AP admin users via 'show wireless-controller globals'.Affected if Unexpected admin accounts exist, or admin accounts were added without authorization, which could indicate an attacker has already exploited this vulnerability to create persistent access.
The device is affected if the FortiAP firmware version falls within any of the listed vulnerable ranges AND the CLI interface is accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.46.4.87.0.4
Apply vendor-provided patches by upgrading FortiAP devices to version 6.4.8+, 7.0.4+, or 7.2.1+ as appropriate for each model. Limit CLI access to trusted personnel and monitor for unauthorized command execution.
FortiAP: 6.4.8+ / 7.0.4+ / 7.2.1+; FortiAP-S: 6.4.8+; FortiAP-U: 6.2.4+; FortiAP-W2: 6.4.8+ / 7.0.4+ / 7.2.1+
- 1. Identify the FortiAP model (FortiAP, FortiAP-S, FortiAP-U, or FortiAP-W2) currently deployed
- 2. Check the current firmware version using FortiOS CLI: `get system status` or through FortiManager/FortiCloud
- 3. For FortiAP: upgrade to version 6.4.8, 7.0.4, or 7.2.1 or later depending on your branch
- 4. For FortiAP-S: upgrade to version 6.4.8 or later
- 5. For FortiAP-U: upgrade to version 6.2.4 or later
- 6. For FortiAP-W2: upgrade to version 6.4.8, 7.0.4, or 7.2.1 or later depending on your branch
- 7. Upload the firmware via FortiOS: go to WiFi Controller > FortiAP > Manage FortiAPs, or use CLI: `execute factoryreset` then `execute upgrade`
- 8. After upgrade, verify the new version: `get system status`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiap
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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