dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-1182

HIGH · 7.0 CVSS v3.1 Published 2024-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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
Uncontrolled Search Path Element vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Hyper Historian versions 10.97.3 and prior, Mitsubishi Electric MC Works64 all versions, Mitsubishi Electric GENESIS32 versions 9.7 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions Hyper Historian versions 10.97.3 and prior, and Mitsubishi Electric Iconics Digital Solutions GENESIS32 versions 9.7 and prior allows a local attacker to execute a malicious code by storing a specially crafted DLL in a specific folder when GENESIS64, ICONICS Suite, Hyper Historian, GENESIS32, and MC Works64 are installed with the Pager agent in the alarm multi-agent notification feature.

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

This is a DLL hijacking vulnerability (Uncontrolled Search Path Element) affecting multiple Mitsubishi Electric industrial software products (GENESIS64, ICONICS Suite, Hyper Historian, GENESIS32, MC Works64) when installed with the Pager agent in the alarm multi-agent notification feature. A local attacker can place a malicious DLL in a specific folder that the application searches, achieving arbitrary code execution with the application's privileges.

MitigationOrganizations should identify and remove any pre-existing malicious DLLs in the affected folder path, implement secure DLL loading practices (explicit paths, hash verification), and consider removing or securing the Pager agent configuration if not required. Review application logs for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:H/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 installed Mitsubishi Electric industrial software
    Check Program Files for GENESIS64, ICONICS Suite, Hyper Historian, GENESIS32, or MC Works64 installations. Use Add/Remove Programs or PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName
    Affected if Any of these products are installed on the system
  2. Verify Pager agent configuration status
    Access the alarm notification configuration within the installed product and check if the Pager agent is enabled or configured
    Affected if The Pager agent is enabled in the alarm multi-agent notification feature
  3. Identify the vulnerable DLL search path
    Locate the folder where the Pager agent searches for DLLs. Check application documentation or configuration files for the DLL search path used by the alarm notification feature
    Affected if A DLL search path is defined and accessible to local users with write permissions
  4. Examine the folder for suspicious DLL files
    List all DLL files in the identified folder. Look for unauthorized or unexpected DLLs that do not belong to the product
    Affected if Unexpected or malicious DLL files are present in the search path folder
  5. Review application logs for exploitation indicators
    Check application and Windows event logs for DLL loading errors, failed load attempts, or suspicious activity related to the Pager agent
    Affected if Logs show DLL loading failures or unauthorized execution attempts

A user is affected if they have any of the listed products installed with the Pager agent enabled and the DLL search path is accessible to local attackers for DLL planting.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should identify and remove any pre-existing malicious DLLs in the affected folder path, implement secure DLL loading practices (explicit paths, hash verification), and consider removing or securing the Pager agent configuration if not required. Review application logs for signs of exploitation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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