dbcve.org
FortiadcApplication · Fortinet

CVE-2023-28000

HIGH · 7.8 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to after 7.0.3 or later.
See remediation →
80/100
Remediation priority · High
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 neutralization of special elements used in an OS command vulnerability [CWE-78] in FortiADC CLI 7.1.0, 7.0.0 through 7.0.3, 6.2.0 through 6.2.4, 6.1 all versions, 6.0 all versions may allow a local and authenticated attacker to execute unauthorized commands via specifically crafted arguments in diagnose system df CLI command.

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

A local authenticated command injection vulnerability in FortiADC CLI allows attackers to inject OS commands through specially crafted arguments to the diagnose system df command. The vulnerability stems from improper neutralization of special elements (CWE-78) in the CLI command parser.

MitigationApply vendor-supplied patches for FortiADC 7.1.0, 7.0.x, 6.2.x, 6.1.x, and 6.0.x. As a compensating control, restrict CLI access to trusted local administrators only.

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
FortiadcApplication
Affected:>= 6.0.0, <= 6.0.4>= 6.1.0, <= 6.1.6>= 6.2.0, <= 6.2.4>= 7.0.0, <= 7.0.3= 7.1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiADC version
    Run 'get system status' in CLI or check Administration > Settings in GUI to obtain the firmware version
    Affected if The version falls within 6.0.0-6.0.4, 6.1.0-6.1.6, 6.2.0-6.2.4, 7.0.0-7.0.3, or 7.1.0
  2. Verify CLI access exists
    Confirm that CLI console or SSH access is enabled and functional on the FortiADC device
    Affected if CLI access is available and the user has valid administrative credentials
  3. Confirm diagnose command accessibility
    Check if the user role includes access to diagnostic commands by reviewing 'diagnose system df' command availability in their profile
    Affected if The authenticated user has permission to execute the diagnose system df command
  4. Check for unauthorized admin accounts
    Review user accounts with administrative privileges using 'get system admin' CLI command
    Affected if Any unexpected or unauthorized admin accounts exist on the system

The environment is affected if FortiADC firmware version is within the ranges 6.0.0-6.0.4, 6.1.0-6.1.6, 6.2.0-6.2.4, 7.0.0-7.0.3, or 7.1.0 AND the device is accessible via CLI to authenticated users with diagnostic command privileges.

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.0.3
Interim mitigation

Apply vendor-supplied patches for FortiADC 7.1.0, 7.0.x, 6.2.x, 6.1.x, and 6.0.x. As a compensating control, restrict CLI access to trusted local administrators only.

Recommended fix High confidence

Upgrade to FortiADC 6.0.5+, 6.1.7+, 6.2.5+, 7.0.4+, or 7.1.1+ depending on your current branch

  1. 1. Identify the current FortiADC version by running: get system status
  2. 2. For FortiADC 6.0.x: Upgrade to version 6.0.5 or later
  3. 3. For FortiADC 6.1.x: Upgrade to version 6.1.7 or later
  4. 4. For FortiADC 6.2.x: Upgrade to version 6.2.5 or later
  5. 5. For FortiADC 7.0.x: Upgrade to version 7.0.4 or later
  6. 6. For FortiADC 7.1.x: Upgrade to version 7.1.1 or later
  7. 7. Download the upgrade image from Fortinet Customer Support portal or FortiGuard
  8. 8. Upload the firmware via FortiADC web UI (System > Firmware) or CLI: execute restore firmware
Caveat Review FortiADC release notes for your target version to check for configuration incompatibilities or deprecated features before upgrading

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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