dbcve.org
Rtx830 FirmwareOperating system · Yamaha

CVE-2020-5548

HIGH · 7.5 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to after 15.02.09 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Yamaha LTE VoIP Router(NVR700W firmware Rev.15.00.15 and earlier), Yamaha Gigabit VoIP Router(NVR510 firmware Rev.15.01.14 and earlier), Yamaha Gigabit VPN Router(RTX810 firmware Rev.11.01.33 and earlier, RTX830 firmware Rev.15.02.09 and earlier, RTX1200 firmware Rev.10.01.76 and earlier, RTX1210 firmware Rev.14.01.33 and earlier, RTX3500 firmware Rev.14.00.26 and earlier, and RTX5000 firmware Rev.14.00.26 and earlier), Yamaha Broadband VoIP Router(NVR500 firmware Rev.11.00.38 and earlier), and Yamaha Firewall(FWX120 firmware Rev.11.03.27 and earlier) allow remote attackers to cause a denial of service 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

Multiple Yamaha network devices (NVR700W, NVR510, RTX series routers, NVR500, FWX120) contain a denial of service vulnerability that can be exploited remotely, causing the device to become unavailable via unspecified vectors.

MitigationApply vendor-supplied firmware updates to all affected devices - NVR700W to Rev.15.00.16+, NVR510 to Rev.15.01.15+, RTX810 to Rev.11.01.34+, RTX830 to Rev.15.02.10+, RTX1200 to Rev.10.01.77+, RTX1210 to Rev.14.01.34+, RTX3500/RTX5000 to Rev.14.00.27+, NVR500 to Rev.11.00.39+, and FWX120 to Rev.11.03.28+. If immediate patching is not possible, restrict network access to management interfaces.

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
Rtx830 FirmwareOperating system
Affected:<= 15.02.09
Nvr510 FirmwareOperating system
Affected:<= 15.01.14
Nvr700w FirmwareOperating system
Affected:<= 15.00.15
Rtx1210 FirmwareOperating system
Affected:<= 14.01.33
Rtx5000 FirmwareOperating system
Affected:<= 14.00.26
Rtx3500 FirmwareOperating system
Affected:<= 14.00.26
Fwx120 FirmwareOperating system
Affected:<= 11.03.27
Rtx810 FirmwareOperating system
Affected:<= 11.01.33

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Yamaha device model
    Access the device admin interface or CLI and retrieve the model name from the system status or device information page. Common CLI command: 'show environment' or check the web UI dashboard for the exact model designation (e.g., NVR700W, NVR510, RTX830, RTX1210, RTX5000, RTX3500, FWX120, RTX810).
    Affected if The device model is one of: NVR700W, NVR510, RTX830, RTX1210, RTX5000, RTX3500, FWX120, or RTX810.
  2. Check the installed firmware version
    Retrieve the firmware version from the device admin interface or CLI. Common CLI command: 'show version' or 'show environment'. The version number is typically displayed in the system information section (e.g., 15.02.09, 15.01.14, 15.00.15, 14.01.33, 14.00.26, 11.03.27, 11.01.33).
    Affected if The installed firmware version is at or below the affected threshold for your specific model.
  3. Verify network accessibility of management interface
    Confirm that the device management interface (web UI, CLI over SSH/Telnet) is reachable from network segments accessible to potential attackers. Check firewall rules and access control lists that permit traffic to the device.
    Affected if The device management interface is exposed to untrusted networks without adequate access restrictions.
  4. Compare firmware version to affected ranges
    Match your identified model and firmware version against the affected ranges: RTX830 <= 15.02.09, NVR510 <= 15.01.14, NVR700W <= 15.00.15, RTX1210 <= 14.01.33, RTX5000 <= 14.00.26, RTX3500 <= 14.00.26, FWX120 <= 11.03.27, RTX810 <= 11.01.33.
    Affected if Your device model and firmware version fall within or below these specific version thresholds.

Your environment is affected if you have any Yamaha NVR700W, NVR510, RTX830, RTX1210, RTX5000, RTX3500, FWX120, or RTX810 devices running firmware at or below the specified version thresholds and their management interfaces are network-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 15.02.09
Interim mitigation

Apply vendor-supplied firmware updates to all affected devices - NVR700W to Rev.15.00.16+, NVR510 to Rev.15.01.15+, RTX810 to Rev.11.01.34+, RTX830 to Rev.15.02.10+, RTX1200 to Rev.10.01.77+, RTX1210 to Rev.14.01.34+, RTX3500/RTX5000 to Rev.14.00.27+, NVR500 to Rev.11.00.39+, and FWX120 to Rev.11.03.28+. If immediate patching is not possible, restrict network access to management interfaces.

Fix this in Rtx830 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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