dbcve.org
AutomationApplication · Ivanti

CVE-2024-9845

HIGH · 7.8 CVSS v3.1 Published 2024-12-11
Fix available
A fix is available. Upgrade to 2024.4.0.1 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
Under specific circumstances, insecure permissions in Ivanti Automation before version 2024.4.0.1 allows a local authenticated attacker to achieve local privilege escalation.

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

Ivanti Automation before version 2024.4.0.1 contains insecure permissions that allow a local authenticated attacker to achieve privilege escalation. The vulnerability requires the attacker to have local access and valid credentials on the target system.

MitigationUpgrade Ivanti Automation to version 2024.4.0.1 or later to remediate this privilege escalation vulnerability.

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:< 2024.4.0.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
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 path
    Check common installation directories such as C:\Program Files\Ivanti\Automation or C:\Program Files (x86)\Ivanti\Automation, or look for the service in Windows Services named 'Ivanti Automation' and check its executable path.
    Affected if The application is installed in a non-standard location or the installation directory is accessible to low-privileged users.
  2. Determine installed Ivanti Automation version
    Locate the installer or check the product version. Common methods: (1) Right-click the executable in the installation folder and select Properties > Details, (2) Check Add/Remove Programs in Windows Control Panel, (3) Query the Windows Registry under HKLM\SOFTWARE\Ivanti\Automation for a Version value.
    Affected if The installed version is earlier than 2024.4.0.1.
  3. Verify file permissions on installation directory
    Right-click the Ivanti Automation installation folder, go to Properties > Security, and review which users and groups have Read, Write, or Full Control permissions. Alternatively, use icacls from an elevated command prompt: icacls "C:\Program Files\Ivanti\Automation"
    Affected if Authenticated users or non-admin groups have write permissions to executable files or configuration files in the installation directory.
  4. Check service binary permissions
    Run 'sc qc IvantiAutomation' from command prompt to see the service binary path, then check permissions on that file using icacls or file properties.
    Affected if The service executable or its associated files are writable by non-privileged users.

You are affected if Ivanti Automation is installed at a version earlier than 2024.4.0.1 AND low-privileged users have write access to service executables or configuration files in the installation directory.

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

Upgrade Ivanti Automation to version 2024.4.0.1 or later to remediate this privilege escalation vulnerability.

Recommended fix High confidence

2024.4.0.1

  1. Back up the current Ivanti Automation installation, configuration, and database
  2. Stop all Ivanti Automation services
  3. Obtain Ivanti Automation version 2024.4.0.1 from the official Ivanti download portal or support site
  4. Run the installer for version 2024.4.0.1 to perform the upgrade
  5. Follow the official upgrade documentation for any additional configuration steps
  6. Start the Ivanti Automation services
  7. Verify the upgrade was successful by checking the version and confirming normal functionality
Caveat Review Ivanti release notes for version 2024.4.0.1 for any compatibility or breaking changes before upgrading

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

Fix this in Automation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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