dbcve.org
DeceptionApplication · Fidelissecurity

CVE-2022-24389

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 “cert_utils” 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 'cert_utils' component allows authenticated users with standard CLI access to execute commands with root privileges on Fidelis Network and Deception platforms. This privilege escalation affects CommandPost, Collector, Sensor, and Sandbox components in versions prior to 9.4.5.

MitigationUpgrade all affected Fidelis components (CommandPost, Collector, Sensor, Sandbox) to version 9.4.5 or later to apply the patched cert_utils module.

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 product version
    Run 'rconfig --version' or check the Fidelis component version through the CLI interface (typically via 'show version' or looking at /opt/fidelis/version file)
    Affected if Version is below 9.4.5 for either Fidelis Deception or Fidelis Network platforms
  2. Confirm the rconfig component is present
    Check for the existence of the rconfig utility on the system, typically located at /usr/bin/rconfig or accessible via CLI command 'rconfig'
    Affected if The rconfig command is available and functional on the system
  3. Verify cert_utils module exists
    Inspect the rconfig installation directory for the cert_utils component, typically found in /opt/fidelis/lib/ or similar library paths, or run 'rconfig -h' to list available modules
    Affected if The cert_utils module is present within the rconfig component
  4. Check CLI user access privileges
    Review the system's CLI user configuration by examining /etc/passwd for users with Fidelis CLI access, or use 'show users' or 'list users' command if available in the Fidelis CLI
    Affected if Standard (non-root) users have CLI access enabled on the system
  5. Audit recent rconfig execution logs
    Review system logs (typically /var/log/messages, /var/log/audit/audit.log, or Fidelis-specific logs in /opt/fidelis/logs/) for rconfig or cert_utils execution history
    Affected if There are log entries showing rconfig cert_utils commands executed by non-root users

The environment is affected if running Fidelis Deception or Network with any component (CommandPost, Collector, Sensor, Sandbox) at a version prior to 9.4.5, where the rconfig utility with cert_utils module is present and standard CLI user accounts exist.

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 all affected Fidelis components (CommandPost, Collector, Sensor, Sandbox) to version 9.4.5 or later to apply the patched cert_utils module.

Recommended fix High confidence

9.4.5

  1. Obtain Fidelis Network and Deception version 9.4.5 or later from the official vendor (fidelissecurity.zendesk.com)
  2. Review vendor release notes and upgrade documentation for version 9.4.5
  3. Create a complete backup of the current Fidelis configuration before upgrading
  4. Apply the upgrade to Fidelis Network and Deception components (CommandPost, Collector, Sensor, and Sandbox)
  5. Verify the installed version is 9.4.5 or later after upgrade completes
  6. Confirm the rconfig cert_utils vulnerability is no longer exploitable

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

Fix this in Deception Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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