CVE-2022-24392
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 “feed_comm_test” value for the “feed” 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 allows remote attackers to execute arbitrary system commands via the web interface by supplying specially crafted values (feed_comm_test) to the feed parameter in HTTP requests. The attacker must have valid authentication credentials to exploit this flaw, and command output is 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 installed Fidelis product versionAccess the CommandPost web interface administrative console and navigate to the Help or About section to view the installed software version. Alternatively, check system documentation or use the product's built-in version check command if available via CLI.Affected if The installed version is any version prior to 9.4.5 for either Fidelis Deception or Fidelis Network.
-
Confirm CommandPost web interface is accessibleVerify that the Fidelis CommandPost web management interface is exposed and reachable on the network. This is typically accessed via HTTPS on port 443 or a configured port.Affected if The web interface is accessible and the product version is below 9.4.5.
-
Check for feed_comm_test endpoint exposureAttempt to access or probe for the feed_comm_test functionality within the web interface. This endpoint handles the feed parameter used in the vulnerability. Review any available API documentation or web interface menus for feed-related testing features.Affected if The feed_comm_test endpoint or similar feed testing feature is present and accessible to authenticated users.
-
Review user account accessExamine the list of users and accounts with access to the CommandPost web interface, particularly those with privileges to access feed configuration or testing features. Check authentication logs for any suspicious session activity.Affected if There are authenticated user accounts with access to feed management features, especially if those accounts have been used recently or show unusual activity patterns.
Your environment is affected if Fidelis Network or Deception CommandPost is running any version prior to 9.4.5 and the web interface with feed testing functionality is accessible to authenticated users.
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
Upgrade to Fidelis Network and Deception version 9.4.5 or later, which contains the vendor patch for this vulnerability. Verify all user sessions and credentials after patching.
Fidelis Network and Deception 9.4.5
- Back up your current Fidelis Network or Deception configuration before proceeding
- Download Fidelis Network/Deception version 9.4.5 or later from the official vendor portal or support channel
- Review the vendor's upgrade documentation for your specific product
- Apply the upgrade following the vendor's recommended upgrade procedure
- After upgrade, verify the installation was successful and the web interface is accessible
- Log in and confirm the 'feed_comm_test' functionality no longer accepts command injection payloads
- Restore configuration from backup if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24392 — 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-24392 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