dbcve.org
FortideceptorApplication · Fortinet

CVE-2022-27487

HIGH · 8.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 3.2.4 / 3.3.3 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
A improper privilege management in Fortinet FortiSandbox version 4.2.0 through 4.2.2, 4.0.0 through 4.0.2 and before 3.2.3 and FortiDeceptor version 4.1.0, 4.0.0 through 4.0.2 and before 3.3.3 allows a remote authenticated attacker to perform unauthorized API calls via crafted HTTP or HTTPS 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

Improper privilege management in FortiSandbox (versions 4.2.0-4.2.2, 4.0.0-4.0.2, before 3.2.3) and FortiDeceptor (4.1.0, 4.0.0-4.0.2, before 3.3.3) allows authenticated attackers to bypass authorization checks and execute unauthorized API calls via crafted HTTP/HTTPS requests.

MitigationUpgrade to vendor-fixed versions (FortiSandbox 3.2.3/4.2.3/4.0.3 or later; FortiDeceptor 3.3.3/4.1.1/4.0.3 or later), or implement proper API authorization validation to ensure users can only access permitted endpoints.

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
FortideceptorApplication
Affected:>= 1.0, < 3.3.3>= 4.0.0, <= 4.0.2= 4.1.0
FortisandboxApplication
Affected:>= 2.5.0, < 3.2.4>= 4.0.0, < 4.0.3>= 4.2.0, < 4.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
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 the installed Fortinet product
    Log into the FortiSandbox or FortiDeceptor web interface and check System > Firmware or use the command 'get system status' via CLI to confirm the product name and exact version number
    Affected if The product is FortiSandbox or FortiDeceptor and the version falls within the affected ranges
  2. Compare installed version to affected ranges
    For FortiSandbox: check if version is >= 2.5.0 and < 3.2.4, OR >= 4.0.0 and < 4.0.3, OR >= 4.2.0 and < 4.2.3. For FortiDeceptor: check if version is >= 1.0 and < 3.3.3, OR >= 4.0.0 and <= 4.0.2, OR = 4.1.0
    Affected if The installed version matches any of the vulnerable version ranges listed
  3. Verify API access is enabled
    Check if the web UI or API service is accessible by attempting to reach the management interface over HTTPS on ports 443 or 8443. Review System > Network > Interface settings to confirm the HTTPS service is enabled on any interface
    Affected if The HTTPS management interface is accessible and the device is reachable over the network
  4. Check for existing user accounts
    Review user accounts in the web UI under User & Device > User or via CLI command 'diagnose system admin list' to confirm there are authenticated users configured
    Affected if There is at least one user account (including admin or limited user accounts) configured on the device

A user is affected if they are running FortiSandbox or FortiDeceptor within the specified vulnerable version ranges AND the web/API interface is accessible with valid user credentials present.

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 3.2.4 / 3.3.3 / 4.0.3 or later
Fixed in 3.2.43.3.34.0.3
Interim mitigation

Upgrade to vendor-fixed versions (FortiSandbox 3.2.3/4.2.3/4.0.3 or later; FortiDeceptor 3.3.3/4.1.1/4.0.3 or later), or implement proper API authorization validation to ensure users can only access permitted endpoints.

Recommended fix High confidence

FortiDeceptor: upgrade to 3.3.3 or 4.0.3+ (not 4.1.0); FortiSandbox: upgrade to 3.2.4, 4.0.3+, or 4.2.3+

  1. 1. Identify the currently installed FortiDeceptor or FortiSandbox version from the device dashboard or CLI using 'get system status'.
  2. 2. For FortiDeceptor: If running version 1.0 to 3.2.x, upgrade to version 3.3.3 or later. If running version 4.0.0 to 4.0.2, upgrade to version 4.0.3 or later. If running version 4.1.0, upgrade to version 4.2.0 or later.
  3. 3. For FortiSandbox: If running version 2.5.0 to 3.2.x, upgrade to version 3.2.4 or later. If running version 4.0.0 to 4.0.2, upgrade to version 4.0.3 or later. If running version 4.2.0 to 4.2.2, upgrade to version 4.2.3 or later.
  4. 4. Download the appropriate firmware from Fortinet Customer Support Portal or FortiGuard: https://www.fortinet.com/support/firmware.
  5. 5. Upload the firmware via FortiDeceptor/FortiSandbox GUI under System > Firmware or via CLI using 'execute firmware upgrade' command.
  6. 6. After upgrade, verify the new version is installed and test that legitimate API functionality still works as expected.
Caveat Review Fortinet release notes for the target version for any configuration or feature changes; test in non-production environment first

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

Fix this in Fortideceptor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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