dbcve.org
AutomationApplication · Ivanti

CVE-2022-44569

HIGH · 7.8 CVSS v3.1 Published 2023-11-03
Fix available
A fix is available. Upgrade to 2023.4 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
A locally authenticated attacker with low privileges can bypass authentication due to insecure inter-process communication.

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 · moderate confidence

This is a local privilege escalation vulnerability where an attacker with low-privilege local authentication can bypass proper authentication mechanisms through insecure inter-process communication. The vulnerability allows the attacker to impersonate higher-privileged sessions or processes by manipulating IPC channels that lack proper validation.

MitigationImplement strong authentication and authorization for all inter-process communication channels, use secure IPC mechanisms with cryptographic verification (e.g., signed messages, shared secrets, or authenticated encryption), and validate privileges at each IPC boundary.

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
AutomationApplication
Affected:< 2023.4

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. Identify Ivanti Automation installation
    Check for Ivanti Automation installation directory or installed programs list on the system. Common locations include C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti
    Affected if Ivanti Automation software is found on the system
  2. Determine installed version
    Locate the version information for Ivanti Automation, typically found in the product's about dialog, registry under HKLM\SOFTWARE\Ivanti, or the main executable properties
    Affected if The version number is lower than 2023.4 (e.g., 2023.3, 2022.x, or earlier)
  3. Verify IPC service status
    Check if the Ivanti Automation service or component that handles inter-process communication is running. Look for services named Ivanti, IPC, or Dispatcher in services.msc
    Affected if IPC-related Ivanti services are running and accessible to low-privilege users
  4. Inspect IPC configuration settings
    Review configuration files in the Ivanti Automation installation directory for IPC-related settings, particularly authentication or authorization parameters
    Affected if IPC channels are configured without cryptographic verification, signed messages, or authenticated encryption
  5. Test local authentication access
    Using a low-privilege local user account, attempt to interact with Ivanti Automation IPC endpoints or observe whether the application permits local non-admin access to sensitive functions
    Affected if Low-privilege users can access or manipulate IPC channels without proper privilege validation

The environment is affected if Ivanti Automation is installed with a version lower than 2023.4 and IPC communication channels lack proper validation mechanisms.

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 2023.4 or later
Fixed in 2023.4
Interim mitigation

Implement strong authentication and authorization for all inter-process communication channels, use secure IPC mechanisms with cryptographic verification (e.g., signed messages, shared secrets, or authenticated encryption), and validate privileges at each IPC boundary.

Recommended fix High confidence

2023.4

  1. Back up your current Ivanti Automation installation and database
  2. Download Ivanti Automation version 2023.4 or later from the official vendor portal (help.ivanti.com)
  3. Apply the upgrade following the vendor's upgrade documentation
  4. Verify the installation completed successfully
  5. Test that authentication mechanisms are functioning properly after the upgrade
Caveat Review release notes for any feature changes between your current version and 2023.4

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

Fix this in Automation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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