CVE-2017-15913 Other in n/a
High 7.8
Published
Updated
Check this codebase for CVE-2017-15913 and fix it if it is affected.
What it is: CVE-2017-15913 is a high-severity vulnerability in n/a, published on 8 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15913 in the wild and no public exploit code.
Affected product: n/a. 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-2017-15913/ (Markdown: https://insights.sbomify.com/CVE-2017-15913/index.md)
The Whale Installer is vulnerable to DLL hijacking, allowing attackers to execute arbitrary code via malicious libraries.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2017-15913?
CVE-2017-15913 is a high-severity vulnerability in n/a, published on 8 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
The Installer in Whale allows DLL hijacking.
Weakness: CWE-426
Which versions are affected by CVE-2017-15913?
It affects 1 product.
Products include Navercorp Whale.
How do I fix CVE-2017-15913?
No fix has been published for CVE-2017-15913 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-15913 being exploited?
There is no known exploitation of CVE-2017-15913 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-r3pp-mxj9-3c69.