FortiapApplication · Fortinet
CVE-2019-15708
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 · uneditedA system command injection vulnerability in the FortiAP-S/W2 6.2.1, 6.2.0, 6.0.5 and below, FortiAP 6.0.5 and below and FortiAP-U below 6.0.0 under CLI admin console may allow unauthorized administrators to run arbitrary system level commands via specially crafted ifconfig 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 · moderate confidenceCommand injection vulnerability in FortiAP CLI allows authenticated administrators to execute arbitrary system commands via specially crafted ifconfig commands. The flaw exists in the parameter validation of ifconfig input within the administrative console.
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.5
Fortiap SApplication
<= 6.0.5= 6.2.0= 6.2.1
Fortiap UApplication
<= 6.0.0
Fortiap W2Application
<= 6.0.5= 6.2.0= 6.2.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 device modelAccess the FortiAP management interface or check the device hardware label to determine if the device is a FortiAP, FortiAP S, FortiAP U, or FortiAP W2 model.Affected if The device model is any of these four FortiAP variants.
-
Check FortiAP firmware versionLog into the FortiAP CLI or web interface and run the command to display the firmware version, typically 'get system status' or 'fwv' in the console, or check via FortiGate wireless controller under Managed FortiAPs.Affected if The firmware version is 6.0.5 or earlier for FortiAP/W2, 6.0.0 or earlier for FortiAP U, or exactly 6.2.0 or 6.2.1 for FortiAP S/W2.
-
Verify CLI administrative access is enabledCheck the FortiAP configuration via FortiGate wireless controller or direct console access to confirm that administrative CLI access (SSH or console) is permitted for administrators.Affected if CLI administrative access is enabled and the device is running an affected version.
-
Confirm ifconfig command is accessibleAccess the FortiAP CLI and verify the 'ifconfig' command is available in the command set, as this is the specific command containing the vulnerability.Affected if The ifconfig command can be executed in the FortiAP CLI on an affected version.
A user is affected if they have any FortiAP, FortiAP S, FortiAP U, or FortiAP W2 device running a firmware version within the affected ranges AND the device CLI interface is accessible to authenticated administrators.
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.
From vendor dataUpdate FortiAP firmware to vendor-supplied patched versions (6.0.6+/6.2.2+). Review and restrict administrative access following least-privilege principles.
Fix this in Fortiap
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15708 — 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-2019-15708 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