dbcve.org
Pr S300ne FirmwareOperating system · Ntt East

CVE-2019-5986

HIGH · 8.8 CVSS v3.1 Published 2019-09-12
Fix available
A fix is available. Upgrade to after 19.41 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-site request forgery (CSRF) vulnerability in Hikari Denwa router/Home GateWay (Hikari Denwa router/Home GateWay provided by NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION PR-S300NE/RT-S300NE/RV-S340NE firmware version Ver. 19.41 and earlier, PR-S300HI/RT-S300HI/RV-S340HI firmware version Ver.19.01.0005 and earlier, PR-S300SE/RT-S300SE/RV-S340SE firmware version Ver.19.40 and earlier, PR-400NE/RT-400NE/RV-440NE firmware version Ver.7.42 and earlier, PR-400KI/RT-400KI/RV-440KI firmware version Ver.07.00.1010 and earlier, PR-400MI/RT-400MI/RV-440MI firmware version Ver. 07.00.1012 and earlier, PR-500KI/RT-500KI firmware version Ver.01.00.0090 and earlier, RS-500KI firmware version Ver.01.00.0070 and earlier, PR-500MI/RT-500MI firmware version Ver.01.01.0014 and earlier, and RS-500MI firmware version Ver.03.01.0019 and earlier, and Hikari Denwa router/Home GateWay provided by NIPPON TELEGRAPH AND TELEPHONE WEST CORPORATION PR-S300NE/RT-S300NE/RV-S340NE firmware version Ver. 19.41 and earlier, PR-S300HI/RT-S300HI/RV-S340HI firmware version Ver.19.01.0005 and earlier, PR-S300SE/RT-S300SE/RV-S340SE firmware version Ver.19.40 and earlier, PR-400NE/RT-400NE/RV-440NE firmware version Ver.7.42 and earlier, PR-400KI/RT-400KI/RV-440KI firmware version Ver.07.00.1010 and earlier, PR-400MI/RT-400MI/RV-440MI firmware version Ver. 07.00.1012 and earlier, PR-500KI/RT-500KI firmware version Ver.01.00.0090 and earlier, and PR-500MI/RT-500MI firmware version Ver.01.01.0011 and earlier) allow remote attackers to hijack the authentication of administrators 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

Cross-site request forgery (CSRF) vulnerability in multiple Hikari Denwa router and Home GateWay models from NTT East and West. The flaw allows remote attackers to hijack administrator authentication by tricking logged-in administrators into visiting malicious sites that send unauthorized requests to the router's web management interface.

MitigationUpdate router firmware to versions newer than those listed (no specific fixed version provided in advisory). As a temporary workaround, avoid browsing untrusted websites while logged into the router admin panel, and log out after each session.

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
Pr S300ne FirmwareOperating system
Affected:<= 19.41
Rt S300ne FirmwareOperating system
Affected:<= 19.41
Rv S340ne FirmwareOperating system
Affected:<= 19.41
Pr S300hi FirmwareOperating system
Affected:<= 19.01.0005
Rt S300hi FirmwareOperating system
Affected:<= 19.01.0005
Rv S340hi FirmwareOperating system
Affected:<= 19.01.0005
Pr S300se FirmwareOperating system
Affected:<= 19.40
Rt S300se FirmwareOperating system
Affected:<= 19.40

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
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 checks

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

  1. Identify router model
    Log into the router web administration interface and look for the model name (typically displayed on the status or system information page), or check the product label on the physical device
    Affected if The model is one of: Pr S300ne, Rt S300ne, Rv S340ne, Pr S300hi, Rt S300hi, Rv S340hi, Pr S300se, or Rt S300se from NTT East
  2. Check firmware version
    In the router web admin interface, navigate to the firmware or system information page and note the displayed firmware version number
    Affected if The firmware version is <= 19.41 for S300ne or S340ne models, <= 19.01.0005 for S300hi or S340hi models, or <= 19.40 for S300se models
  3. Confirm web management interface is enabled
    Access the router admin panel via its IP address (commonly 192.168.1.1 or 192.168.0.1) in a web browser
    Affected if The web management interface is accessible and does not require additional authentication beyond the admin login
  4. Verify CSRF protection status
    Inspect the router admin pages for anti-CSRF tokens or referrer validation in forms and AJAX requests. Check the HTML source of admin pages for the presence of unique tokens in state-changing requests
    Affected if No anti-CSRF tokens are present in forms and the router accepts requests without proper referrer validation

A user is affected if they own one of the listed NTT East router models with firmware at or below the specified version limits and the web management interface is accessible.

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 19.41
Interim mitigation

Update router firmware to versions newer than those listed (no specific fixed version provided in advisory). As a temporary workaround, avoid browsing untrusted websites while logged into the router admin panel, and log out after each session.

Fix this in Pr S300ne Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA0.5 h
4.5 hours of engineering $800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5986 — 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-2019-5986 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