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

CVE-2024-10068

HIGH · 7.8 CVSS v3.1 Published 2024-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability was found in OpenSight Software FlashFXP 5.4.0.3970. It has been classified as critical. Affected is an unknown function in the library libcrypto-1_1.dll of the file FlashFXP.exe. The manipulation leads to uncontrolled search path. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

A DLL hijacking vulnerability exists in FlashFXP 5.4.0.3970 where the application loads libcrypto-1_1.dll from an insecure search path, allowing a local attacker to place a malicious DLL in a directory the application searches for libraries, resulting in arbitrary code execution.

MitigationEnsure FlashFXP is run from a secure directory and avoid storing or downloading untrusted files in directories where the application searches for DLLs. Implement secure DLL loading using absolute paths or manifest-based binding.

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
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. Locate FlashFXP installation directory
    Search for FlashFXP installation folders - common paths include C:\Program Files\FlashFXP\ or C:\Program Files (x86)\FlashFXP\. Check Start Menu shortcuts or registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\FlashFXP or HKEY_CURRENT_USER\SOFTWARE\FlashFXP for the installation path.
    Affected if FlashFXP is installed and the application loads libcrypto-1_1.dll from a directory writable by a local attacker.
  2. Identify installed FlashFXP version
    Open the FlashFXP installation directory and locate a version file (version.txt, ver.txt) or right-click on FlashFXP.exe, select Properties, and check the Details tab for Product Version.
    Affected if The installed version matches 5.4.0.3970 or falls within an unknown range that contains this vulnerability.
  3. Check for vulnerable DLL in application directory
    Examine the FlashFXP installation directory for the presence of libcrypto-1_1.dll. Also check if this DLL exists in directories that may be in the Windows DLL search order (current working directory, system directories, PATH directories).
    Affected if libcrypto-1_1.dll is loaded from a directory that is not secured against local attacker placement of malicious DLLs.
  4. Verify DLL search path configuration
    Run FlashFXP and monitor DLL loading using Process Monitor (procmon.exe) from Sysinternals - filter by Process Name FlashFXP.exe and Operation Load Image. Observe which paths Windows searches when FlashFXP loads libcrypto-1_1.dll.
    Affected if The application loads libcrypto-1_1.dll from a directory outside the secure installation folder, indicating insecure DLL search path usage.
  5. Assess directory write access
    Identify directories in the DLL search path for FlashFXP (particularly the application directory and current working directory). Use icacls.exe to check if standard users have write permissions to these directories.
    Affected if Standard users can write to any directory that FlashFXP searches for libcrypto-1_1.dll, allowing DLL hijacking.

A user is affected if FlashFXP version 5.4.0.3970 is installed and the application loads libcrypto-1_1.dll from a directory where a local attacker can place a malicious DLL.

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

Ensure FlashFXP is run from a secure directory and avoid storing or downloading untrusted files in directories where the application searches for DLLs. Implement secure DLL loading using absolute paths or manifest-based binding.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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