dbcve.org
DeceptionApplication · Fidelissecurity

CVE-2022-24393

HIGH · 8.8 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 9.4.5 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
Vulnerability in Fidelis Network and Deception CommandPost enables authenticated command injection through the web interface using the “check_vertica_upgrade” value for the “cpIp” 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 confidence

Authenticated command injection vulnerability in Fidelis Network and Deception CommandPost allows remote attackers to execute arbitrary OS commands via the web interface by supplying the 'check_vertica_upgrade' value through the 'cpIp' parameter. The vulnerability is exploitable through specially crafted HTTP requests and returns command output in the HTTP response, requiring only a valid authenticated session.

MitigationApply the vendor patch or update to version 9.4.5 or later to remediate this vulnerability. Until patched, restrict network access to the CommandPost web interface to trusted IP addresses only and enforce strict least-privilege access controls.

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
DeceptionApplication
Affected:< 9.4.5
NetworkApplication
Affected:< 9.4.5

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 Fidelis product and version
    Access the CommandPost web interface and navigate to the system information or about page, or check the installed packages via command line if you have backend access. Compare the version number to the affected range (versions prior to 9.4.5).
    Affected if The installed version is less than 9.4.5 for either Fidelissecurity Deception or Fidelissecurity Network.
  2. Confirm CommandPost web interface is accessible
    Attempt to reach the CommandPost web interface over HTTP/HTTPS from a network location. Check if port 443 or the web application's port is open and responding.
    Affected if The CommandPost web interface is exposed and reachable from network locations.
  3. Verify if authentication is currently enforced
    Attempt to access the CommandPost web interface without providing credentials. Observe whether the application redirects to a login page or returns an authentication error.
    Affected if The web interface allows unauthenticated access or has weak authentication controls.
  4. Inspect HTTP request parameters for command injection vectors
    If you have access to web request logs or can intercept traffic, examine requests involving the 'cpIp' parameter and look for any 'check_vertica_upgrade' values being passed.
    Affected if Requests containing 'check_vertica_upgrade' values in the 'cpIp' parameter are present in logs or traffic captures.

Your environment is affected if you are running Fidelissecurity Deception or Network versions prior to 9.4.5 AND the CommandPost web interface is accessible over the network, regardless of authentication status since exploitation requires only a valid authenticated session.

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 9.4.5 or later
Fixed in 9.4.5
Interim mitigation

Apply the vendor patch or update to version 9.4.5 or later to remediate this vulnerability. Until patched, restrict network access to the CommandPost web interface to trusted IP addresses only and enforce strict least-privilege access controls.

Recommended fix High confidence

9.4.5

  1. Upgrade Fidelis Network to version 9.4.5 or later
  2. Upgrade Fidelis Deception to version 9.4.5 or later
  3. Verify the upgrade was successful by logging into CommandPost
  4. After upgrade, validate that the check_vertica_upgrade functionality no longer accepts arbitrary command injection via the cpIp parameter

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

Fix this in Deception Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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