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

CVE-2024-28953

MEDIUM · 6.7 CVSS v3.1 Published 2024-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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 in some EMON software before version 11.44 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 · moderate confidence

Uncontrolled search path vulnerability in EMON software versions before 11.44 allows an authenticated local attacker to perform DLL hijacking or path injection, potentially escalating privileges by placing malicious code in the application's search path.

MitigationUpdate EMON software to version 11.44 or later to obtain the patched binaries. If immediate patching is not feasible, restrict write access to application directories and monitor for suspicious DLL placement.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 if EMON software is installed
    Search for EMON installation directories in common locations such as C:\Program Files\EMON, C:\Program Files (x86)\EMON, or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for EMON entries
    Affected if EMON software is found installed on the system
  2. Determine the installed EMON version
    Locate the EMON executable (typically named emon.exe or similar) and right-click to view Properties, then check the Details tab for the File Version, or run 'wmic product get name,version' if EMON was installed via an installer
    Affected if The installed version is lower than 11.44 or the version cannot be determined (assume affected)
  3. Inspect application directory for unauthorized DLL files
    Examine all DLL files present in the EMON installation directory for any unexpected or newly created DLLs that do not belong to the standard EMON installation
    Affected if Unexpected DLL files are found in the EMON installation directory, especially those with recent creation timestamps
  4. Check file permissions on EMON directories
    Right-click the EMON installation folder, select Properties, go to the Security tab, and verify which users and groups have Write or Modify permissions
    Affected if Any non-admin users or groups have Write or Modify permissions to the EMON installation directory
  5. Review DLL search order behavior
    Check if the EMON application loads DLLs from its own directory first by examining application logs or using process monitoring tools to observe DLL loading activity
    Affected if The application loads DLLs from its installation directory without validation (vulnerable search path behavior)

The system is affected if EMON software is installed with a version lower than 11.44 and the application directory has writable permissions or contains unauthorized DLL files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update EMON software to version 11.44 or later to obtain the patched binaries. If immediate patching is not feasible, restrict write access to application directories and monitor for suspicious DLL placement.

Recommended fix Moderate confidence

EMON software version 11.44 or later

  1. Identify the currently installed EMON software version on the affected system
  2. Download EMON software version 11.44 or later from Intel's official website
  3. Verify the integrity of the downloaded package using checksums if available
  4. Close any running instances of EMON software
  5. Install the updated EMON software version 11.44 or later
  6. Verify the installed version matches the expected fixed version
  7. Restart any services or applications that use EMON if necessary

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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