# CVE-2016-4850: Code injection in n/a

> Man-in-the-middle attackers can execute arbitrary code on LINE for Windows clients, requiring users to upgrade to a secure version.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j35m-x776-7v62

## What is CVE-2016-4850?

CVE-2016-4850 is a high-severity code injection vulnerability in Linecorp Line, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LINE for Windows before 4.8.3 allows man-in-the-middle attackers to execute arbitrary code.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-4850?

It affects 1 product.


Products: Linecorp Line.

## How do I fix CVE-2016-4850?

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

## Is CVE-2016-4850 being exploited?

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

## Other vulnerabilities in Linecorp Line

- [CVE-2023-45559](https://insights.sbomify.com/CVE-2023-45559/): Information disclosure in n/a (high 8.2)
- [CVE-2023-43305](https://insights.sbomify.com/CVE-2023-43305/): Information disclosure in n/a (high 8.2)
- [CVE-2023-43300](https://insights.sbomify.com/CVE-2023-43300/): Information disclosure in n/a (high 8.2)
- [CVE-2023-43301](https://insights.sbomify.com/CVE-2023-43301/): Code injection in n/a (high 8.2)
- [CVE-2023-43302](https://insights.sbomify.com/CVE-2023-43302/): Information disclosure in n/a (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4850 and fix it if it is affected.

What it is: CVE-2016-4850 is a high-severity code injection vulnerability in Linecorp Line, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4850 in the wild and no public exploit code.

Affected product: Linecorp Line. 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-2016-4850/ (Markdown: https://insights.sbomify.com/CVE-2016-4850/index.md)
```

## Sources

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

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