CVE-2022-24390
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 rconfig “remote_text_file” enables an attacker with user level access to the CLI to inject user 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 confidenceA command injection vulnerability in rconfig's 'remote_text_file' functionality allows an authenticated user with CLI access to inject and execute commands at the user privilege level in Fidelis Network and Deception products (CommandPost, Collector, Sensor, Sandbox) and neighboring Fidelis components.
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 installationLocate and check the Fidelis product installed (CommandPost, Collector, Sensor, or Sandbox). Run 'rpm -qa | grep fidelis' or check the product documentation for version information.Affected if Any Fidelis Deception or Network component version is found to be below 9.4.5
-
Determine installed product versionExecute the version check command for the specific Fidelis product (for example, 'fidelis --version' or check the about/license screen in the admin console).Affected if The installed version is lower than 9.4.5 for either Fidelissecurity Deception or Fidelissecurity Network
-
Verify CLI access configurationCheck if CLI access is enabled for authenticated users in the Fidelis admin interface or configuration files. Look for settings related to 'remote_text_file' or CLI access permissions.Affected if CLI access is enabled for authenticated users, which is required for the command injection to be exploitable
-
Audit recent CLI session logsReview CLI access and command execution logs in /var/log/ or the Fidelis logging directory for any unauthorized or suspicious command executions from authenticated sessions.Affected if Unexpected or malicious commands appear in CLI logs that were not initiated by legitimate administrators
A user is affected if their Fidelis Deception or Network installation is version < 9.4.5 AND has CLI access enabled for authenticated users, as the command injection requires both conditions to be exploitable.
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 Fidelis Network and Deception installations to version 9.4.5 or later to apply the available patches and updates.
9.4.5 or later
- Obtain Fidelis Network and Deception version 9.4.5 or later from official Fidelis Security channels (fidelissecurity.zendesk.com or your Fidelis support representative)
- Review the upgrade documentation and release notes specific to your deployment architecture (CommandPost, Collector, Sensor, Sandbox components)
- Apply the upgrade to all affected Fidelis Network and Deception installations running versions prior to 9.4.5
- Verify the upgrade was successful by checking the version number in the product interface
- Confirm the rconfig remote_text_file functionality is working correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24390 — 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-24390 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