FortideceptorApplication · Fortinet
CVE-2022-38373
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 input during web page generation vulnerability [CWE-79] in FortiDeceptor management interface 4.2.0, 4.1.0 through 4.1.1, 4.0.2 may allow an authenticated user to perform a cross site scripting (XSS) attack via sending requests with specially crafted lure resource ID.
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 cross-site scripting (XSS) vulnerability in FortiDeceptor management interface allows authenticated users to inject malicious scripts via specially crafted lure resource IDs. The vulnerability stems from improper input neutralization when the lure resource ID is displayed back to users.
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
= 4.0.2= 4.1.0= 4.1.1= 4.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Check FortiDeceptor firmware versionAccess the FortiDeceptor management interface and navigate to System > Firmware or check the dashboard for the version. Alternatively, use the CLI command 'get system status' to retrieve the installed version.Affected if The installed version is 4.0.2, 4.1.0, 4.1.1, or 4.2.0
-
Confirm management interface accessibilityReview network configuration and firewall policies to determine if the FortiDeceptor management interface (HTTPS port) is accessible from untrusted network segments or the internet.Affected if The management interface is exposed to untrusted or external users without proper access controls
-
Locate lure resource configurationIn the FortiDeceptor management interface, navigate to the Deception or Lures section. Identify any configured lure resources and note their resource ID parameters.Affected if Lure resources are configured and in use within the deception environment
-
Inspect resource ID handlingWhen viewing or editing lure resources in the interface, observe how the resource ID field is rendered and whether special characters are treated as plain text or interpreted.Affected if The resource ID field accepts and displays unsanitized input without proper encoding
The environment is affected if FortiDeceptor version matches the affected list AND the management interface is accessible to authenticated users who can configure or view lure resources with injectable resource IDs.
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 dataApply vendor-provided patches for FortiDeceptor versions 4.2.0, 4.1.0-4.1.1, and 4.0.2. Until patched, restrict management interface access to trusted users only and monitor for suspicious activity.
Fix this in Fortideceptor
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38373 — 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-38373 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