CVE-2022-24394
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 · uneditedVulnerability in Fidelis Network and Deception CommandPost enables authenticated command injection through the web interface using the “update_checkfile” value for the “filename” parameter. The vulnerability could allow a specially crafted HTTP request to execute system commands on the CommandPost and return results in an HTTP response via an authenticated session. The vulnerability is present in Fidelis Network and Deception versions prior to 9.4.5. Patches and updates are available to address this vulnerability.
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 confidenceAuthenticated command injection vulnerability in Fidelis Network and Deception CommandPost web interface. Attackers can execute arbitrary system commands by submitting specially crafted HTTP requests with malicious 'filename' parameter values to the 'update_checkfile' endpoint. Results are returned in the HTTP response.
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< 9.4.5< 9.4.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Fidelis product and versionLocate the Fidelis installation and retrieve the installed version number. This is typically visible in the CommandPost login page footer, admin console, or via system information commands provided by the product documentation.Affected if The installed version is Fidelissecurity Deception or Fidelissecurity Network and the version is below 9.4.5
-
Confirm CommandPost web interface is accessibleVerify that the CommandPost web interface is enabled and network-accessible. This is typically accessed over HTTPS on port 443 or a custom port. Attempt to reach the login page.Affected if The web interface is exposed and accessible (this is required for the vulnerability to be exploitable)
-
Inspect HTTP access logs for update_checkfile requestsExamine the CommandPost web server access logs (typically found in /var/log/ or product-specific log directories) for POST requests to the 'update_checkfile' endpoint. Look for requests containing unusual patterns in the 'filename' parameter such as semicolons, pipe symbols, backticks, or command separators.Affected if Logs show POST requests to update_checkfile with suspicious filename parameter values containing command injection patterns
-
Check for unauthorized command execution indicatorsReview system logs, audit logs, or CommandPost logs for evidence of unexpected command execution, spawned processes, or privilege escalation that correlates with the timing of any suspicious update_checkfile requests.Affected if Logs or system artifacts show unexpected command execution that cannot be attributed to legitimate administrative actions
A user is affected if they run Fidelissecurity Deception or Network with a version lower than 9.4.5 and have the CommandPost web interface exposed, with evidence of suspicious update_checkfile requests or unauthorized command execution in logs.
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 · scoped9.4.5
Update Fidelis Network and Deception to version 9.4.5 or later to apply vendor patches. Alternatively, restrict web interface access to only trusted administrative users and monitor for suspicious requests.
Fidelis Network and Deception version 9.4.5
- Obtain Fidelis Network and Deception version 9.4.5 or later from Fidelis Security's official support portal (fidelissecurity.zendesk.com)
- Review the upgrade documentation provided by Fidelis Security for CommandPost
- Ensure you have a valid backup of the current configuration
- Initiate the upgrade process for CommandPost component via the management interface or CLI as documented
- Verify the upgrade completed successfully
- Confirm the version is now 9.4.5 or later
- Validate that the update_checkfile functionality no longer allows command injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24394 — 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-24394 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