# CVE-2016-1228: Cross-site request forgery in n/a

> Remote attackers can hijack user authentication on NTT Hikari Denwa routers via CSRF, requiring firmware upgrades to mitigate.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jul 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fp88-gm7q-v687

## What is CVE-2016-1228?

CVE-2016-1228 is a high-severity vulnerability in n/a, published on 3 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability on NTT EAST Hikari Denwa routers with firmware PR-400MI, RT-400MI, and RV-440MI 07.00.1006 and earlier and NTT WEST Hikari Denwa routers with firmware PR-400MI, RT-400MI, and RV-440MI 07.00.1005 and earlier allows remote attackers to hijack the authentication of arbitrary users.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 7 products.


Products: Ntt-East Pr-400mi Firmware, Ntt-East Rt-400mi Firmware, Ntt-East Rv-440mi Firmware, Ntt-West Pr-400mi, Ntt-West Pr-400mi Firmware, Ntt-West Rt-400mi Firmware, Ntt-West Rv-440mi Firmware.

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

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

## Is CVE-2016-1228 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-1227](https://insights.sbomify.com/CVE-2016-1227/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1228 is a high-severity vulnerability in n/a, published on 3 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-1228 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-2016-1228/ (Markdown: https://insights.sbomify.com/CVE-2016-1228/index.md)
```

## Sources

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

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