CVE-2019-16647 Other in n/a
High 7.2
Published
Updated
Check this codebase for CVE-2019-16647 and fix it if it is affected.
What it is: CVE-2019-16647 is a high-severity vulnerability in n/a, published on 29 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16647 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-2019-16647/ (Markdown: https://insights.sbomify.com/CVE-2019-16647/index.md)
Attackers can execute arbitrary code via unquoted search paths in Maxthon browser on Windows.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2019-16647?
CVE-2019-16647 is a high-severity vulnerability in n/a, published on 29 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Unquoted Search Path in Maxthon 5.1.0 to 5.2.7 Browser for Windows.
Weakness: CWE-428
Which versions are affected by CVE-2019-16647?
It affects 1 product.
Products include Maxthon Maxthon Browser.
How do I fix CVE-2019-16647?
No fix has been published for CVE-2019-16647 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-16647 being exploited?
There is no known exploitation of CVE-2019-16647 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-8pp9-95mf-4fhv.