dbcve.org
Performance ManagerApplication · Ivanti

CVE-2024-11597

HIGH · 7.8 CVSS v3.1 Published 2024-12-11
Fix available
A fix is available. Upgrade to 2023.3 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 Performance Manager before version 2024.3 HF1, 2024.1 HF1, or 2023.3 HF1 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

Insecure permissions in Ivanti Performance Manager allow a local authenticated attacker to achieve local privilege escalation, likely through misconfigured file or service permissions that can be exploited to gain elevated system access.

MitigationUpgrade Ivanti Performance Manager to version 2024.3 HF1, 2024.1 HF1, or 2023.3 HF1 to remediate the permission vulnerabilities.

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
Performance ManagerApplication
Affected:< 2023.3= 2023.3= 2024.1= 2024.3

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. Verify Ivanti Performance Manager is installed
    Check for Ivanti Performance Manager in the list of installed programs via Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Select-Object Name, Version' in PowerShell to list installed software
    Affected if Ivanti Performance Manager appears in the installed programs list
  2. Determine the installed version
    Open the Windows registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductGUID} or check the application binary properties (right-click the main executable > Properties > Details)
    Affected if The version displayed is 2023.3, 2024.1, 2024.3, or any version lower than 2023.3
  3. Compare version against affected ranges
    Note the exact version number from the previous step and compare it to the affected list: versions < 2023.3, 2023.3, 2024.1, or 2024.3
    Affected if The installed version matches any of these (2024.3 HF1, 2024.1 HF1, and 2023.3 HF1 are NOT affected)
  4. Check for local authenticated access
    Verify whether the system allows local user authentication to the affected Ivanti Performance Manager service
    Affected if Local user accounts exist with access to the Ivanti Performance Manager service or its data directories

You are affected if Ivanti Performance Manager is installed and the installed version is 2023.3, 2024.1, 2024.3, or any version below 2023.3.

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.3 or later
Fixed in 2023.3
Interim mitigation

Upgrade Ivanti Performance Manager to version 2024.3 HF1, 2024.1 HF1, or 2023.3 HF1 to remediate the permission vulnerabilities.

Recommended fix High confidence

2024.3 HF1 (or 2024.1 HF1 or 2023.3 HF1 depending on your current version)

  1. 1. Identify the currently installed Ivanti Performance Manager version
  2. 2. Download the appropriate HotFix (HF1) for your version from Ivanti support portal (forums.ivanti.com)
  3. 3. Back up the current Ivanti Performance Manager configuration and database
  4. 4. Apply the hotfix according to Ivanti's official installation documentation
  5. 5. Restart the Ivanti Performance Manager services as required by the hotfix
  6. 6. Verify the installation was successful by checking the version number
  7. 7. Confirm the fix by reviewing file permissions on the affected directories
Caveat Review release notes for any configuration changes required when moving to the HF1 version

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

Fix this in Performance Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
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,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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