dbcve.org
Wn Ax1167gr FirmwareOperating system · Iodata

CVE-2017-2282

MEDIUM · 6.8 CVSS v3.0 Published 2017-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Buffer overflow in WN-AX1167GR firmware version 3.00 and earlier allows an attacker to execute arbitrary 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

Buffer overflow vulnerability in WN-AX1167GR router firmware versions 3.00 and earlier allows remote attackers to execute arbitrary commands by overflowing a buffer through unspecified vectors.

MitigationUpdate firmware to a version newer than 3.00. If no update is available, restrict network access to the device or disable vulnerable services.

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
Wn Ax1167gr FirmwareOperating system
Affected:= 3.00

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/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 the device model
    Check the router label, web interface, or admin panel for the exact model number WN-AX1167GR
    Affected if Device is not the Iodata WN-AX1167GR model
  2. Check the installed firmware version
    Access the router admin web interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to the System or Status page to view the firmware version, or use the router's command-line interface if available
    Affected if Firmware version is 3.00 or any version earlier than 3.00
  3. Verify remote management exposure
    Check the router admin interface under Advanced Settings or Security settings for Remote Management/Administration features that allow access from WAN (external networks)
    Affected if Remote management from WAN is enabled and firmware version is 3.00 or earlier
  4. Review accessible services
    Check which services are exposed to the network (HTTP, HTTPS, telnet, SSH) by scanning the router's external IP with tools like nmap or by reviewing port forwarding/DMZ settings in the admin interface
    Affected if Exposed network services exist and firmware version is 3.00 or earlier

The device is affected if it is an Iodata WN-AX1167GR router running firmware version 3.00 or any earlier version, with network-accessible services.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update firmware to a version newer than 3.00. If no update is available, restrict network access to the device or disable vulnerable services.

Fix this in Wn Ax1167gr Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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