CVE-2021-38514 : Detail

CVE-2021-38514

2.7
/
Low
0.05%V3
Network
2021-08-10
21h54 +00:00
2021-08-10
21h54 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Certain NETGEAR devices are affected by authentication bypass. This affects D3600 before 1.0.0.72, D6000 before 1.0.0.72, D6100 before 1.0.0.63, D6200 before 1.1.00.34, D6220 before 1.0.0.48, D6400 before 1.0.0.86, D7000 before 1.0.1.70, D7000v2 before 1.0.0.52, D7800 before 1.0.1.56, D8500 before 1.0.3.44, DC112A before 1.0.0.42, DGN2200v4 before 1.0.0.108, DGND2200Bv4 before 1.0.0.108, EX2700 before 1.0.1.48, EX3700 before 1.0.0.76, EX3800 before 1.0.0.76, EX6000 before 1.0.0.38, EX6100 before 1.0.2.24, EX6100v2 before 1.0.1.76, EX6120 before 1.0.0.42, EX6130 before 1.0.0.28, EX6150v1 before 1.0.0.42, EX6150v2 before 1.0.1.76, EX6200 before 1.0.3.88, EX6200v2 before 1.0.1.72, EX6400 before 1.0.2.136, EX7000 before 1.0.0.66, EX7300 before 1.0.2.136, EX8000 before 1.0.1.180, RBK50 before 2.1.4.10, RBR50 before 2.1.4.10, RBS50 before 2.1.4.10, RBK40 before 2.1.4.10, RBR40 before 2.1.4.10, RBS40 before 2.1.4.10, RBW30 before 2.2.1.204, PR2000 before 1.0.0.28, R6020 before 1.0.0.38, R6080 before 1.0.0.38, R6050 before 1.0.1.18, JR6150 before 1.0.1.18, R6120 before 1.0.0.46, R6220 before 1.1.0.86, R6250 before 1.0.4.34, R6300v2 before 1.0.4.32, R6400 before 1.0.1.44, R6400v2 before 1.0.2.62, R6700 before 1.0.1.48, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900v2 before 1.2.0.36, R6900 before 1.0.1.48, R7000 before 1.0.9.34, R6900P before 1.3.1.64, R7000P before 1.3.1.64, R7100LG before 1.0.0.48, R7300DST before 1.0.0.70, R7500v2 before 1.0.3.38, R7800 before 1.0.2.52, R7900 before 1.0.3.8, R8000 before 1.0.4.28, R7900P before 1.4.1.30, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, R9000 before 1.0.3.10, RBS40V before 2.2.0.58, RBK50V before 2.2.0.58, WN2000RPTv3 before 1.0.1.32, WN2500RPv2 before 1.0.1.54, WN3000RPv3 before 1.0.2.78, WN3100RPv2 before 1.0.0.66, WNDR3400v3 before 1.0.1.22, WNDR3700v4 before 1.0.2.102, WNDR4300v1 before 1.0.2.104, WNDR4300v2 before 1.0.0.56, WNDR4500v3 before 1.0.0.56, WNR2000v5 (R2000) before 1.0.0.66, WNR2020 before 1.1.0.62, WNR2050 before 1.1.0.62, WNR3500Lv2 before 1.2.0.62, and XR500 before 2.3.2.22.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE Other No informations.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 2.4 LOW CVSS:3.1/AC:L/AV:A/A:N/C:L/I:N/PR:H/S:U/UI:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Adjacent

The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.
V3.1 2.7 LOW CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V3.1 2.4 LOW CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Adjacent

The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 4 AV:N/AC:L/Au:S/C:P/I:N/A:N [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Netgear>>D3600_firmware >> Version To (excluding) 1.0.0.72

Netgear>>D3600 >> Version -

Configuraton 0

Netgear>>D6000_firmware >> Version To (excluding) 1.0.0.72

Netgear>>D6000 >> Version -

Configuraton 0

Netgear>>D6100_firmware >> Version To (excluding) 1.0.0.63

Netgear>>D6100 >> Version -

Configuraton 0

Netgear>>D6200_firmware >> Version To (excluding) 1.1.00.34

Netgear>>D6200 >> Version -

Configuraton 0

Netgear>>D6220_firmware >> Version To (excluding) 1.0.0.48

Netgear>>D6220 >> Version -

Configuraton 0

Netgear>>D6400_firmware >> Version To (excluding) 1.0.0.86

Netgear>>D6400 >> Version -

Configuraton 0

Netgear>>D7000_firmware >> Version To (excluding) 1.0.1.70

Netgear>>D7000 >> Version -

Configuraton 0

Netgear>>D7000_firmware >> Version To (excluding) 1.0.0.52

Netgear>>D7000 >> Version v2

Configuraton 0

Netgear>>D7800_firmware >> Version To (excluding) 1.0.1.56

Netgear>>D7800 >> Version -

Configuraton 0

Netgear>>D8500_firmware >> Version To (excluding) 1.0.3.44

Netgear>>D8500 >> Version -

Configuraton 0

Netgear>>Dc112a_firmware >> Version To (excluding) 1.0.0.42

Netgear>>Dc112a >> Version -

Configuraton 0

Netgear>>Dgn2200_firmware >> Version To (excluding) 1.0.0.108

Netgear>>Dgn2200 >> Version v4

Configuraton 0

Netgear>>Dgnd2200b_firmware >> Version To (excluding) 1.0.0.108

Netgear>>Dgnd2200b >> Version v4

Configuraton 0

Netgear>>Ex2700_firmware >> Version To (excluding) 1.0.1.48

Netgear>>Ex2700 >> Version -

Configuraton 0

Netgear>>Ex3700_firmware >> Version To (excluding) 1.0.0.76

Netgear>>Ex3700 >> Version -

Configuraton 0

Netgear>>Ex3800_firmware >> Version To (excluding) 1.0.0.76

Netgear>>Ex3800 >> Version -

Configuraton 0

Netgear>>Ex6000_firmware >> Version To (excluding) 1.0.0.38

Netgear>>Ex6000 >> Version -

Configuraton 0

Netgear>>Ex6100_firmware >> Version To (excluding) 1.0.2.24

Netgear>>Ex6100 >> Version -

Configuraton 0

Netgear>>Ex6100_firmware >> Version To (excluding) 1.0.1.76

Netgear>>Ex6100 >> Version v2

Configuraton 0

Netgear>>Ex6120_firmware >> Version To (excluding) 1.0.0.42

Netgear>>Ex6120 >> Version -

Configuraton 0

Netgear>>Ex6130_firmware >> Version To (excluding) 1.0.0.28

Netgear>>Ex6130 >> Version -

Configuraton 0

Netgear>>Ex6150_firmware >> Version To (excluding) 1.0.0.42

Netgear>>Ex6150 >> Version v1

Configuraton 0

Netgear>>Ex6150_firmware >> Version To (excluding) 1.0.1.76

Netgear>>Ex6150 >> Version v2

Configuraton 0

Netgear>>Ex6200_firmware >> Version To (excluding) 1.0.3.88

Netgear>>Ex6200 >> Version -

Configuraton 0

Netgear>>Ex6200_firmware >> Version To (excluding) 1.0.1.72

Netgear>>Ex6200 >> Version v2

Configuraton 0

Netgear>>Ex6400_firmware >> Version To (excluding) 1.0.2.136

Netgear>>Ex6400 >> Version -

Configuraton 0

Netgear>>Ex7000_firmware >> Version To (excluding) 1.0.0.66

Netgear>>Ex7000 >> Version -

Configuraton 0

Netgear>>Ex7300_firmware >> Version To (excluding) 1.0.2.136

Netgear>>Ex7300 >> Version -

Configuraton 0

Netgear>>Ex8000_firmware >> Version To (excluding) 1.0.1.180

Netgear>>Ex8000 >> Version -

Configuraton 0

Netgear>>Rbk50_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbk50 >> Version -

Configuraton 0

Netgear>>Rbr50_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbr50 >> Version -

Configuraton 0

Netgear>>Rbs50_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbs50 >> Version -

Configuraton 0

Netgear>>Rbk40_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbk40 >> Version -

Configuraton 0

Netgear>>Rbr40_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbr40 >> Version -

Configuraton 0

Netgear>>Rbs40_firmware >> Version To (excluding) 2.1.4.10

Netgear>>Rbs40 >> Version -

Configuraton 0

Netgear>>Rbw30_firmware >> Version To (excluding) 2.2.1.204

Netgear>>Rbw30 >> Version -

Configuraton 0

Netgear>>Pr2000_firmware >> Version To (excluding) 1.0.0.28

Netgear>>Pr2000 >> Version -

Configuraton 0

Netgear>>R6020_firmware >> Version To (excluding) 1.0.0.38

Netgear>>R6020 >> Version -

Configuraton 0

Netgear>>R6080_firmware >> Version To (excluding) 1.0.0.38

Netgear>>R6080 >> Version -

Configuraton 0

Netgear>>R6050_firmware >> Version To (excluding) 1.0.1.18

Netgear>>R6050 >> Version -

Configuraton 0

Netgear>>Jr6150_firmware >> Version To (excluding) 1.0.1.18

Netgear>>Jr6150 >> Version -

Configuraton 0

Netgear>>R6120_firmware >> Version To (excluding) 1.0.0.46

Netgear>>R6120 >> Version -

Configuraton 0

Netgear>>R6220_firmware >> Version To (excluding) 1.1.0.86

Netgear>>R6220 >> Version -

Configuraton 0

Netgear>>R6250_firmware >> Version To (excluding) 1.0.4.34

Netgear>>R6250 >> Version -

Configuraton 0

Netgear>>R6300_firmware >> Version To (excluding) 1.0.4.32

Netgear>>R6300 >> Version v2

Configuraton 0

Netgear>>R6400_firmware >> Version To (excluding) 1.0.1.44

Netgear>>R6400 >> Version -

Configuraton 0

Netgear>>R6400_firmware >> Version To (excluding) 1.0.2.62

Netgear>>R6400 >> Version v2

Configuraton 0

Netgear>>R6700_firmware >> Version To (excluding) 1.0.1.48

Netgear>>R6700 >> Version -

Configuraton 0

Netgear>>R6700_firmware >> Version To (excluding) 1.2.0.36

Netgear>>R6700 >> Version v2

Configuraton 0

Netgear>>R6800_firmware >> Version To (excluding) 1.2.0.36

Netgear>>R6800 >> Version -

Configuraton 0

Netgear>>R6900_firmware >> Version To (excluding) 1.2.0.36

Netgear>>R6900 >> Version v2

Configuraton 0

Netgear>>R6900_firmware >> Version To (excluding) 1.0.1.48

Netgear>>R6900 >> Version -

Configuraton 0

Netgear>>R7000_firmware >> Version To (excluding) 1.0.9.34

Netgear>>R7000 >> Version -

Configuraton 0

Netgear>>R6900p_firmware >> Version To (excluding) 1.3.1.64

Netgear>>R6900p >> Version -

Configuraton 0

Netgear>>R7000p_firmware >> Version To (excluding) 1.3.1.64

Netgear>>R7000p >> Version -

Configuraton 0

Netgear>>R7100lg_firmware >> Version To (excluding) 1.0.0.48

Netgear>>R7100lg >> Version -

Configuraton 0

Netgear>>R7300dst_firmware >> Version To (excluding) 1.0.0.70

Netgear>>R7300dst >> Version -

Configuraton 0

Netgear>>R7500_firmware >> Version To (excluding) 1.0.3.38

Netgear>>R7500 >> Version v2

Configuraton 0

Netgear>>R7800_firmware >> Version To (excluding) 1.0.2.52

Netgear>>R7800 >> Version -

Configuraton 0

Netgear>>R7900_firmware >> Version To (excluding) 1.0.3.8

Netgear>>R7900 >> Version -

Configuraton 0

Netgear>>R8000_firmware >> Version To (excluding) 1.0.4.28

Netgear>>R8000 >> Version -

Configuraton 0

Netgear>>R7900p_firmware >> Version To (excluding) 1.4.1.30

Netgear>>R7900p >> Version -

Configuraton 0

Netgear>>R8000p_firmware >> Version To (excluding) 1.4.1.30

Netgear>>R8000p >> Version -

Configuraton 0

Netgear>>R8300_firmware >> Version To (excluding) 1.0.2.128

Netgear>>R8300 >> Version -

Configuraton 0

Netgear>>R8500_firmware >> Version To (excluding) 1.0.2.128

Netgear>>R8500 >> Version -

Configuraton 0

Netgear>>R9000_firmware >> Version To (excluding) 1.0.3.10

Netgear>>R9000 >> Version -

Configuraton 0

Netgear>>Rbs40v_firmware >> Version To (excluding) 2.2.0.58

Netgear>>Rbs40v >> Version -

Configuraton 0

Netgear>>Rbk50v_firmware >> Version To (excluding) 2.2.0.58

    Netgear>>Rbk50v >> Version -

    Configuraton 0

    Netgear>>Wn2000rpt_firmware >> Version To (excluding) 1.0.1.32

    Netgear>>Wn2000rpt >> Version v3

    Configuraton 0

    Netgear>>Wn2500rp_firmware >> Version To (excluding) 1.0.1.54

    Netgear>>Wn2500rp >> Version v2

    Configuraton 0

    Netgear>>Wn3000rp_firmware >> Version To (excluding) 1.0.2.78

    Netgear>>Wn3000rp >> Version v3

    Configuraton 0

    Netgear>>Wn3100rp_firmware >> Version To (excluding) 1.0.0.66

    Netgear>>Wn3100rp >> Version v2

    Configuraton 0

    Netgear>>Wndr3400_firmware >> Version To (excluding) 1.0.1.22

    Netgear>>Wndr3400 >> Version v3

    Configuraton 0

    Netgear>>Wndr3700_firmware >> Version To (excluding) 1.0.2.102

    Netgear>>Wndr3700 >> Version v4

    Configuraton 0

    Netgear>>Wndr4300_firmware >> Version To (excluding) 1.0.2.104

    Netgear>>Wndr4300 >> Version v1

    Configuraton 0

    Netgear>>Wndr4300_firmware >> Version To (excluding) 1.0.0.56

    Netgear>>Wndr4300 >> Version v2

    Configuraton 0

    Netgear>>Wndr4500_firmware >> Version To (excluding) 1.0.0.56

    Netgear>>Wndr4500 >> Version v3

    Configuraton 0

    Netgear>>Wnr2000_firmware >> Version To (excluding) 1.0.0.66

    Netgear>>Wnr2000 >> Version v5

    Configuraton 0

    Netgear>>Wnr2020_firmware >> Version To (excluding) 1.1.0.62

    Netgear>>Wnr2020 >> Version -

    Configuraton 0

    Netgear>>Wnr2050_firmware >> Version To (excluding) 1.1.0.62

    Netgear>>Wnr2050 >> Version -

    Configuraton 0

    Netgear>>Wnr3500l_firmware >> Version To (excluding) 1.2.0.62

    Netgear>>Wnr3500l >> Version v2

    Configuraton 0

    Netgear>>Xr500_firmware >> Version To (excluding) 2.3.2.22

    Netgear>>Xr500 >> Version -

    References