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

CVE-2024-50583

MEDIUM · 6.3 CVSS v3.1 Published 2024-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Whale browser Installer before 3.1.0.0 allows an attacker to execute a malicious DLL in the user environment due to improper permission settings.

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

The Whale browser installer before version 3.1.0.0 is vulnerable to DLL hijacking due to improper permission settings in the installation process. An attacker with local access could place a malicious DLL in a directory from which the installer loads DLLs during execution, resulting in arbitrary code execution with the privileges of the user running the installer.

MitigationUpgrade to Whale browser Installer version 3.1.0.0 or later which contains corrected permission settings and secure DLL loading behavior.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Check if Whale browser is installed
    Search for Whale browser installation directories in typical locations: %ProgramFiles%\Whale, %LocalAppData%\Whale, or check Registry under HKLM\SOFTWARE\Whale and HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Whale entries
    Affected if Whale browser is found installed on the system
  2. Identify the installed Whale browser installer version
    Locate the installer executable (typically named WhaleBrowserSetup.exe or similar) in the installation directory or in %Temp% after a download. Right-click the installer and select Properties, then check the Details tab for the version number
    Affected if The version number displayed is lower than 3.1.0.0 (for example, 3.0.x.x or earlier)
  3. Verify the installer version in installed programs
    Open Windows Settings > Apps > Installed apps, search for 'Whale', and note the version number displayed for the Whale browser installation
    Affected if The installed version shown is before 3.1.0.0
  4. Inspect installation directory permissions
    Right-click the Whale browser installation folder (such as C:\Program Files\Whale or C:\Users\%username%\AppData\Local\Whale), select Properties > Security, and verify that standard users or low-privileged accounts do not have Write or Modify permissions to the directory
    Affected if Standard users have Write or Modify permissions to directories where the installer loads DLLs, allowing potential DLL hijacking
  5. Check for unexpected DLLs in installation directories
    Review all .dll files present in the Whale browser installation folder and any subdirectories, noting any unfamiliar or recently added DLLs that do not match expected Whale browser components
    Affected if Unexpected or suspicious DLL files are present in directories from which the installer loads libraries

The system is affected if Whale browser installer version is present and is lower than 3.1.0.0, or if the installation directory permissions allow standard users to write to locations where the installer loads DLLs.

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

Upgrade to Whale browser Installer version 3.1.0.0 or later which contains corrected permission settings and secure DLL loading behavior.

Recommended fix Low confidence

Whale browser Installer 3.1.0.0 or later

  1. Upgrade the Whale browser Installer to version 3.1.0.0 or later to remediate the DLL hijack vulnerability
  2. Ensure you download the installer from the official Whale browser website or verified distribution channels to avoid counterfeit packages
  3. After upgrading, verify that the installer no longer loads DLLs from untrusted locations

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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