CVE-2016-1228
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability affecting specific NTT Hikari Denwa router models (PR-400MI, RT-400MI, RV-440MI) with firmware versions 07.00.1006 (NTT EAST) and 07.00.1005 (NTT WEST) and earlier. The flaw allows remote attackers to forge authenticated requests by tricking authenticated users into visiting malicious pages, enabling complete authentication hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 07.00.1005all versions<= 07.00.1005<= 07.00.1005= 07.00.1006<= 07.00.1006<= 07.00.1006CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelAccess the router's web administration interface or check the device label/documentation to confirm the exact model number (PR-400MI, RT-400MI, or RV-440MI) and whether it is NTT EAST or NTT WEST variantAffected if Model is PR-400MI, RT-400MI, or RV-440MI from NTT EAST or NTT WEST
-
Determine firmware versionLog into the router web interface and navigate to the status or firmware information page to view the installed firmware version numberAffected if Firmware version is 07.00.1005 or earlier (NTT WEST) or 07.00.1006 or earlier (NTT EAST) - note that PR-400MI NTT EAST is affected only at exactly 07.00.1006
-
Verify web management interface exposureConfirm whether the router's web-based administration interface is accessible from network segments where users could be tricked into visiting malicious pages (typically port 80/443 on the router's LAN or WAN IP)Affected if The authenticated web interface is reachable from any network where untrusted websites could be accessed by authenticated users
-
Check for CSRF protectionsInspect the router's web interface HTML source or form submissions to verify if anti-CSRF tokens or referrer validation are implemented in administrative actionsAffected if No anti-CSRF tokens or referrer checks are present in administrative forms
-
Confirm active authentication sessionsDetermine if the router allows persistent administrative sessions that could be exploited through CSRF while the user remains logged inAffected if Administrative sessions remain active without short timeout or require re-authentication for each action
You are affected if you have a PR-400MI, RT-400MI, or RV-440MI router from NTT EAST or NTT WEST running firmware at or below the affected version numbers AND the router web interface is accessible to users who could be targeted by malicious web pages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied firmware updates to patch the CSRF vulnerability. Until updates are available, consider network segmentation to limit router exposure and implement web application firewall rules to detect anomalous authenticated requests.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data