# CVE-2024-50583: Other in Naver Whale browser Installer

> An attacker can execute malicious code via DLL hijacking in the Naver Whale browser installer due to improper permission settings.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-44fh-qw29-wqf9

## What is CVE-2024-50583?

CVE-2024-50583 is a medium-severity vulnerability in Naver Whale browser Installer, published on 25 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2024-50583?


## How do I fix CVE-2024-50583?

No fix has been published for CVE-2024-50583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-50583 being exploited?

There is no known exploitation of CVE-2024-50583 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50583 and fix it if it is affected.

What it is: CVE-2024-50583 is a medium-severity vulnerability in Naver Whale browser Installer, published on 25 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50583 in the wild and no public exploit code.

Affected product: Naver Whale browser Installer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50583/ (Markdown: https://insights.sbomify.com/CVE-2024-50583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50583
- OSV: https://osv.dev/vulnerability/CVE-2024-50583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50583/
Summaries are generated and may contain mistakes; the official description above is the record.