CyberSecBulletin
CVE-2016-10174Exploited in the wildNVD status: Analyzed

NETGEAR WNR2000v5 Router Buffer Overflow

CVE-2016-10174 is a critical-severity buffer copy without checking size of input vulnerability in D6100 Firmware from NETGEAR, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. CISA added it to the Known Exploited Vulnerabilities catalogue on March 25, 2022, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of D6100 Firmware you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply updates per vendor instructions.
  3. Read the advisory on kb.netgear.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
NETGEARD6100 FirmwareNot specified in the recordNot stated
NETGEARD7000 FirmwareNot specified in the recordNot stated
NETGEARD7800 FirmwareNot specified in the recordNot stated
NETGEARJnr1010v2 FirmwareNot specified in the recordNot stated
NETGEARJnr3300 FirmwareNot specified in the recordNot stated
NETGEARJwnr2010v5 FirmwareNot specified in the recordNot stated
NETGEARR2000 FirmwareNot specified in the recordNot stated
NETGEARR6100 FirmwareNot specified in the recordNot stated
NETGEARR6220 FirmwareNot specified in the recordNot stated
NETGEARR7500 FirmwareNot specified in the recordNot stated
NETGEARR7500v2 FirmwareNot specified in the recordNot stated
NETGEARWndr3700v4 FirmwareNot specified in the recordNot stated
NETGEARWndr3800 FirmwareNot specified in the recordNot stated
NETGEARWndr4300 FirmwareNot specified in the recordNot stated
NETGEARWndr4300v2 FirmwareNot specified in the recordNot stated
NETGEARWndr4500v3 FirmwareNot specified in the recordNot stated
NETGEARWndr4700 FirmwareNot specified in the recordNot stated
NETGEARWnr1000v2 FirmwareNot specified in the recordNot stated
NETGEARWnr1000v4 FirmwareNot specified in the recordNot stated
NETGEARWnr2000v3 FirmwareNot specified in the recordNot stated
NETGEARWnr2000v4 FirmwareNot specified in the recordNot stated
NETGEARWnr2000v5 FirmwareNot specified in the recordNot stated
NETGEARWnr2020 FirmwareNot specified in the recordNot stated
NETGEARWnr2050 FirmwareNot specified in the recordNot stated
NETGEARWnr2200 FirmwareNot specified in the recordNot stated

Version data comes from NVD's product matching; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalNVD
CVSS 3.19.8CriticalCISA (ADP)
CVSS 2.010.0HighNVD

Official description

The NETGEAR WNR2000v5 router contains a buffer overflow in the hidden_lang_avi parameter when invoking the URL /apply.cgi?/lang_check.html. This buffer overflow can be exploited by an unauthenticated attacker to achieve remote code execution.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Technical write-ups (may include proof of concept)

Other vulnerabilities in D6100 Firmware

All D6100 Firmware vulnerabilities

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.