DeceptionApplication · Fidelissecurity

CVE-2022-24388

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 rconfig “date” enables an attacker with user level access to the CLI to inject root level commands into Fidelis Network and Deception CommandPost, Collector, Sensor, and Sandbox components as well as neighboring Fidelis components. 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

A command injection vulnerability in the rconfig 'date' function allows authenticated users with CLI access to execute root-level commands on Fidelis Network and Deception products (CommandPost, Collector, Sensor, and Sandbox) prior to version 9.4.5. The attacker exploits the date parameter to inject OS commands, achieving privilege escalation from user to root.

MitigationUpgrade Fidelis Network and Deception components to version 9.4.5 or later, or apply the available patches to remediate the command injection vulnerability.

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 installed Fidelis products
    Search for Fidelis Network or Deception product installations on the system. Look for directories or services related to CommandPost, Collector, Sensor, or Sandbox components.
    Affected if Fidelis Network or Deception products are found on the system
  2. Determine installed product version
    Use the system's package manager, CLI version command, or check configuration files to obtain the exact version number of the Fidelis product.
    Affected if The installed version is lower than 9.4.5
  3. Verify CLI access availability
    Check if the rconfig CLI utility is accessible on the system. Determine if authenticated CLI users can access the rconfig tool.
    Affected if CLI access to rconfig is available to authenticated users
  4. Confirm date function accessibility
    Test or inspect whether the 'date' function within the rconfig CLI tool is accessible and functional for authenticated users.
    Affected if The rconfig 'date' function is accessible via CLI

A user is affected if they have Fidelis Network or Deception products installed with a version lower than 9.4.5 and the rconfig CLI with its 'date' function is accessible to authenticated users.

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

Upgrade Fidelis Network and Deception components to version 9.4.5 or later, or apply the available patches to remediate the command injection vulnerability.

Recommended fix High confidence

9.4.5 or later

  1. Obtain Fidelis Network and Deception version 9.4.5 or later from the official Fidelis Security support portal or vendor distribution channels
  2. Review the upgrade documentation specific to your deployment topology (CommandPost, Collector, Sensor, or Sandbox components)
  3. Execute the upgrade procedure according to Fidelis documentation, ensuring backup of current configuration
  4. Verify the version post-upgrade matches 9.4.5 or later
  5. Confirm the 'date' command functionality no longer permits privilege escalation
Caveat Review release notes for any configuration or compatibility changes between your current version and 9.4.5; test in non-production environment first

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

Fix this in Deception Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24388 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