CVE-2024-9167
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 · uneditedUnder specific circumstances, insecure permissions in Ivanti Velocity License Server before version 5.2 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 confidenceIvanti Velocity License Server versions prior to 5.2 contain insecure file system permissions that allow a locally authenticated attacker to modify service executable paths or configuration files, enabling escalation to elevated (SYSTEM) privileges.
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>= 5.1, < 5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti Velocity License Server is installedCheck for the presence of the Ivanti Velocity License Server service using 'services.msc' or via command line: 'sc query velocitylicenseserver' or 'Get-Service -Name *velocity*' in PowerShellAffected if The service named 'Ivanti Velocity License Server' or similar is found on the system
-
Identify installed versionLocate the License Server installation directory (commonly under Program Files or Program Files x86) and check the version of the main executable, or run 'wmic product get name,version' filtered for Ivanti VelocityAffected if The installed version is 5.1.x or any version lower than 5.2 (note: version 5.2 itself is NOT affected)
-
Verify service is runningOpen services.msc and check if the Ivanti Velocity License Server service status is Running, or use 'sc query state= all' and search for the serviceAffected if The service is currently running - exploitation requires the service to be active
-
Examine service executable path permissionsUse icacls or accesschk to inspect permissions on the service executable path (found in service properties > Path to executable). Check if standard users have Write or Write DAC permissions on the .exe file or its parent folderAffected if Standard authenticated users have modification/write access to the service executable or its containing directory, allowing path hijacking
-
Check configuration file permissionsLocate configuration files in the License Server installation directory. Use icacls to examine ACLs: 'icacls "C:\Path\To\Velocity\*" | findstr /i "Users"' to see ifUsers group has write accessAffected if Authenticated users can modify configuration files in the application directory, enabling privilege escalation
A system is affected if Ivanti Velocity License Server version 5.1.x (or any version >=5.1 but <5.2) is installed and running, and standard users have write access to the service executable or its configuration files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.2
Upgrade Ivanti Velocity License Server to version 5.2 or later to obtain the security patch addressing the permission vulnerability.
5.2
- Back up the current Velocity License Server configuration and data before upgrading
- Download Velocity License Server version 5.2 or later from the official Ivanti download portal or support site
- Stop the Velocity License Server service
- Install version 5.2 of Velocity License Server following standard installation procedures
- Verify that the installation completed successfully and permissions are properly configured
- Start the Velocity License Server service and confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9167 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9167 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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