CVE-2022-0997
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 · uneditedImproper file permissions in the CommandPost, Collector, and Sensor components of Fidelis Network and Deception enables an attacker with local, administrative access to the CLI to modify affected script files, which could result in arbitrary commands being run as root upon subsequent logon by a root user. 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 local privilege escalation vulnerability in Fidelis Network and Deception versions prior to 9.4.5 allows an attacker with local administrative CLI access to modify script files in CommandPost, Collector, and Sensor components due to improper file permissions. These modified scripts then execute with root privileges upon subsequent root user logon.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 and versionRun 'fidelis --version' or check the About section in the Fidelis management console to determine if the installed version is Network or Deception, and note the exact version number.Affected if The installed version is Network or Deception and the version number is less than 9.4.5.
-
Verify presence of affected componentsCheck if CommandPost, Collector, or Sensor components are installed on the system. These are typically listed in the Fidelis deployment configuration or can be found by listing running services related to Fidelis.Affected if Any of the CommandPost, Collector, or Sensor components are present on the system.
-
Examine script file permissions in affected componentsLocate script directories within the CommandPost, Collector, and Sensor installation paths. Use 'ls -la' or 'icacls' (Windows) to inspect permissions on .sh, .py, .pl, or similar script files. Verify whether unprivileged users can write to these script files.Affected if Non-root or non-admin users have write permissions on script files in the component directories.
-
Check for local administrative CLI accessDetermine if local administrative CLI access is available to non-privileged users. Check user group memberships and sudo/root access policies for the Fidelis system.Affected if Non-root users have administrative CLI access to the Fidelis system.
-
Inspect script files for unauthorized modificationsReview script files in the CommandPost, Collector, and Sensor directories for any unexpected or unauthorized changes. Compare file hashes against known-good baselines if available, or check for suspicious content.Affected if Script files show modifications that were not authored by legitimate administrators, or contain unexpected commands.
A system is affected if it runs Fidelis Network or Deception version below 9.4.5 with CommandPost, Collector, or Sensor components installed, and those components contain script files writable by non-privileged users with local CLI access.
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 obtain the patched file permissions. If immediate patching is not possible, restrict administrative CLI access and monitor for unauthorized script modifications.
9.4.5
- Identify which Fidelis component(s) are in use: CommandPost, Collector, or Sensor
- Take a backup of current configuration and note current version
- Upgrade the affected component(s) to version 9.4.5 or later using the Fidelis update mechanism
- After upgrade, verify file permissions on script files in the affected components have been corrected
- Confirm the product version reflects 9.4.5 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0997 — 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-0997 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