dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2022-30121

MEDIUM · 6.7 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 2021.1.1 or later.
See remediation →
69/100
Remediation priority · Elevated
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
The “LANDesk(R) Management Agent” service exposes a socket and once connected, it is possible to launch commands only for signed executables. This is a security bug that allows a limited user to get escalated admin privileges on their system.

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

The LANDesk Management Agent service exposes a network socket that allows authenticated connections. The vulnerability allows a limited/low-privilege user to connect to this socket and execute commands that result in privilege escalation to administrator, despite the service requiring signed executables for execution.

MitigationApply the vendor-provided security update or patch for CVE-2022-30121 to the LANDesk Management Agent. If no patch is available, consider disabling the service or restricting network access until remediation is possible.

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
Endpoint ManagerApplication
Affected:< 2021.1.1= 2021.1.1

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 if LANDesk/Ivanti endpoint client is installed
    Check for the LANDesk Management Agent or Ivanti Endpoint Manager service: On Windows, run 'sc query' or look in Services.msc for 'LANDesk Management Agent' or 'Ivanti Endpoint Manager' service entries. Also check for installation directories such as C:\Program Files\LANDesk or C:\Program Files\Ivanti.
    Affected if The service or installation directory exists on the system
  2. Determine the installed version
    Check the version of the LANDesk/Ivanti service. On Windows, run 'sc qc "LANDesk Management Agent"' or check the version property of the executable in the installation directory (typically in \Program Files\LANDesk\ or \Program Files\Ivanti\). Compare the version number to the affected range: versions < 2021.1.1 or exactly 2021.1.1.
    Affected if The installed version is lower than 2021.1.1 or exactly equals 2021.1.1
  3. Verify the service is running
    Check if the LANDesk Management Agent service is currently running. On Windows, run 'sc query "LANDesk Management Agent"' or use Task Manager to look for related processes.
    Affected if The service is running and thus exposing the vulnerable network socket
  4. Confirm network socket exposure
    Check for listening network ports associated with the LANDesk service. Run 'netstat -an | findstr LISTENING' and look for ports typically used by LANDesk (common ports include 9535, 9595, or custom-configured management ports). Also check if the Windows Firewall allows incoming connections on these ports.
    Affected if The service is listening on a network port accessible to authenticated users on the local network

The system is affected if Ivanti Endpoint Manager or LANDesk Management Agent is installed with version 2021.1.1 or earlier and the service is running with an exposed network socket.

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

Apply the vendor-provided security update or patch for CVE-2022-30121 to the LANDesk Management Agent. If no patch is available, consider disabling the service or restricting network access until remediation is possible.

Recommended fix Moderate confidence

Endpoint Manager 2021.1.2 or later

  1. Verify current Endpoint Manager agent version by checking the LANDesk Management Agent service properties
  2. Download the latest Endpoint Manager version (2021.1.2 or later) from the Ivanti customer portal or support site
  3. Review release notes for any prerequisites or migration requirements
  4. Create a backup of current configuration or take note of current settings
  5. Deploy the upgrade through your normal management infrastructure or manual installation
  6. Verify the service starts correctly and the vulnerability is resolved by confirming the socket is no longer exposed to unprivileged users
  7. Test that legitimate management functions still work as expected
Caveat No specific breaking changes mentioned in available documentation; standard upgrade precautions apply (backup config, test in staging first)

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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