dbcve.org
License Manager For FleximApplication · Intel

CVE-2024-24977

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 11.19.5.0 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
Uncontrolled search path for some Intel(R) License Manager for FLEXlm product software before version 11.19.5.0 may allow an authenticated user to potentially enable escalation of privilege via local access.

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

Intel License Manager for FLEXlm before version 11.19.5.0 contains an uncontrolled search path vulnerability allowing an authenticated local user to potentially execute arbitrary code with elevated privileges via DLL search order hijacking or binary planting.

MitigationUpdate Intel License Manager for FLEXlm to version 11.19.5.0 or later to obtain the vendor patch.

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
License Manager For FleximApplication
Affected:< 11.19.5.0

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. Confirm Intel License Manager for FLEXlm is installed
    Check for the presence of the Intel License Manager installation directory, typically found under C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\. Look for folders named 'Intel License Manager' or 'FlexLM' containing lmgrd.exe or vendor daemons.
    Affected if The software is installed on the system.
  2. Identify installed version
    Locate the lmgrd.exe or Intel License Manager executable, right-click and select Properties, then check the Details tab for the File Version. Alternatively, run 'lmgrd -v' or 'lmgrd -version' from the installation directory command prompt.
    Affected if The version number is lower than 11.19.5.0.
  3. Verify if the service runs with elevated privileges
    Open Services (services.msc), locate the Intel License Manager service (often named 'Intel FLEXlm License Manager' or similar), right-click and select Properties. Check the 'Log on as' setting to see if it runs as Local System, a domain account, or another privileged account.
    Affected if The service runs as Local System or another account with elevated privileges.
  4. Check for writable directories in executable search path
    Review the installation directory permissions by right-clicking the folder, selecting Properties, then Security tab. Verify which users have Write or Modify permissions. Also check if the PATH environment variable includes any user-writable directories that could be used for DLL hijacking.
    Affected if Non-admin users have Write permissions to directories in the executable search path.

The system is affected if Intel License Manager for FLEXlm version 11.19.5.0 or later is NOT installed AND the service runs with elevated privileges from a location with exploitable search path permissions.

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

Update Intel License Manager for FLEXlm to version 11.19.5.0 or later to obtain the vendor patch.

Recommended fix High confidence

11.19.5.0 or later

  1. Identify the currently installed version of Intel(R) License Manager for FLEXlm on the system
  2. Navigate to Intel's official support or download portal for License Manager for FLEXlm products
  3. Download version 11.19.5.0 or a later stable release of Intel License Manager for FLEXlm
  4. Execute the installer with appropriate administrative privileges
  5. Follow the on-screen prompts to complete the upgrade installation
  6. Restart any License Manager services if prompted
  7. Verify the installed version is 11.19.5.0 or later to confirm the remediation

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

Fix this in License Manager For Flexim Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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