dbcve.org
Rt 400mi FirmwareOperating system · Ntt East

CVE-2016-1227

HIGH · 7.2 CVSS v3.1 Published 2016-07-03
Fix available
A fix is available. Upgrade to after 07.00.1006 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
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 allow remote authenticated users to execute arbitrary OS commands via unspecified vectors.

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 · moderate confidence

This vulnerability allows remote authenticated users to execute arbitrary operating system commands on affected NTT Hikari Denwa routers (PR-400MI, RT-400MI, RV-440MI) via unspecified vectors, likely through a command injection flaw in the web management interface. The attack requires valid credentials, indicating this is an authenticated command injection vulnerability.

MitigationUpdate router firmware to versions beyond 07.00.1006 (NTT EAST) or 07.00.1005 (NTT WEST). If firmware updates are unavailable, restrict administrative web interface access to trusted IP addresses or VPN networks to reduce attack surface.

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
Rt 400mi FirmwareOperating system
Affected:<= 07.00.1006
Pr 400mi FirmwareOperating system
Affected:<= 07.00.1005
Rt 400mi FirmwareOperating system
Affected:<= 07.00.1005
Rv 440mi FirmwareOperating system
Affected:<= 07.00.1005
Pr 400mi FirmwareOperating system
Affected:<= 07.00.1006
Rv 440mi FirmwareOperating system
Affected:<= 07.00.1006

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Locate the model number on the router device label or log into the web management interface and check the status or system information page for the model designation (PR-400MI, RT-400MI, or RV-440MI)
    Affected if Model is PR-400MI, RT-400MI, or RV-440MI
  2. Determine router provider
    Identify whether the router is from NTT East or NTT West - this is usually visible on the device label, in the administrative interface, or corresponds to your internet service provider region
    Affected if Router is from NTT East or NTT West
  3. Check firmware version
    Access the router web management interface and navigate to the status, system information, or firmware version page to retrieve the currently installed firmware version number
    Affected if Firmware version is at or below 07.00.1006 for NTT East models, or at or below 07.00.1005 for NTT West models
  4. Verify web interface exposure
    Determine if the router web management interface is accessible from the internet or untrusted networks by checking port 80/443 forwardings on upstream devices or testing external connectivity to the router IP
    Affected if Web management interface is exposed to untrusted networks (internet-facing)
  5. Confirm authentication status
    Review router access control settings and verify whether default credentials or predictable credentials are in use, as successful authentication is required for exploitation
    Affected if Default or weak credentials are configured, or administrative access is not properly restricted

You are affected if you have a PR-400MI, RT-400MI, or RV-440MI router running firmware version 07.00.1006 or lower (NTT East) or 07.00.1005 or lower (NTT West), with the web management interface accessible and valid credentials available to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 07.00.1006
Interim mitigation

Update router firmware to versions beyond 07.00.1006 (NTT EAST) or 07.00.1005 (NTT WEST). If firmware updates are unavailable, restrict administrative web interface access to trusted IP addresses or VPN networks to reduce attack surface.

Fix this in Rt 400mi Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1227 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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