# CVE-2016-1203: Code injection in SaAT Netizen

> A remote attacker can perform a man-in-the-middle attack to force the execution of malicious files via the SaAT Netizen installer.

- **Severity:** High 8.1 (`CVSS:3.1/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:** 31 Oct 2023
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-q385-6v59-7vxv

## What is CVE-2016-1203?

CVE-2016-1203 is a high-severity code injection vulnerability in NetMove Corporation SaAT Netizen, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper file verification vulnerability in SaAT Netizen installer ver.1.2.0.424 and earlier, and SaAT Netizen ver.1.2.0.8 (Build427) and earlier allows a remote unauthenticated attacker to conduct a man-in-the-middle attack. A successful exploitation may result in a malicious file being downloaded and executed.

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

It affects 2 products.


Products: Saat Netizen, Saat Netizen Installer.

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

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

## Is CVE-2016-1203 being exploited?

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

## Other vulnerabilities in NetMove Corporation SaAT Netizen

- [CVE-2017-2206](https://insights.sbomify.com/CVE-2017-2206/): Privilege escalation in The installer of SaAT Netizen (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1203 is a high-severity code injection vulnerability in NetMove Corporation SaAT Netizen, published on 31 Oct 2023. 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-1203 in the wild and no public exploit code.

Affected product: NetMove Corporation SaAT Netizen. 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-1203/ (Markdown: https://insights.sbomify.com/CVE-2016-1203/index.md)
```

## Sources

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

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