DeceptionApplication · Fidelissecurity

CVE-2022-0486

HIGH · 7.8 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 9.4.5 or later.
See remediation →
80/100
Remediation priority · High
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
Improper file permissions in the CommandPost, Collector, Sensor, and Sandbox components of Fidelis Network and Deception enables an attacker with local, administrative access to the CLI to modify affected files and enable escalation of privileges equivalent to the 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 confidence

Improper file permissions in the CommandPost, Collector, Sensor, and Sandbox components of Fidelis Network and Deception allow a local administrative CLI user to modify critical system files and escalate privileges to root by exploiting insufficient permission controls.

MitigationApply the vendor patch and upgrade to Fidelis Network and Deception version 9.4.5 or later to remediate the improper file permissions.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Fidelis product version
    Access the CLI or administrative interface and run the command to display the system version (e.g., 'show version' or check the about/system info section in the management console)
    Affected if The displayed version is lower than 9.4.5 for either Fidelissecurity Deception or Fidelissecurity Network
  2. Identify active Fidelis components
    Check which components are installed and running: CommandPost, Collector, Sensor, and Sandbox. This may be visible in the management console under system status or via CLI commands like 'show components'
    Affected if Any of the affected components (CommandPost, Collector, Sensor, or Sandbox) are present and running on a version lower than 9.4.5
  3. Verify local administrative CLI access exists
    Confirm whether local administrative CLI user accounts exist on the system. Check for users with admin or root-level CLI access permissions
    Affected if Local administrative CLI accounts exist on an affected version, as this is required to exploit the privilege escalation
  4. Inspect critical system file permissions
    Review file permissions on critical system files and directories within the Fidelis installation. Look for files writable by non-root users that should be restricted
    Affected if Any critical system files under the Fidelis components are found to be writable by local administrative (non-root) users

The environment is affected if Fidelis Network or Deception version is below 9.4.5 and local administrative CLI access exists, enabling potential privilege escalation through improper file permissions.

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 and upgrade to Fidelis Network and Deception version 9.4.5 or later to remediate the improper file permissions.

Recommended fix Moderate confidence

9.4.5

  1. Upgrade Fidelis Network and Deception installations to version 9.4.5 or later to resolve the improper file permissions vulnerability
  2. Verify the upgrade was successful by confirming the version number in the system

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

Fix this in Deception Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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