CVE-2017-18769 : Detail

CVE-2017-18769

4.6
/
Medium
A01-Broken Access Control
0.07%V3
Physical
2020-04-22
12h54 +00:00
2020-04-22
12h54 +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 an attacker's ability to read arbitrary files. This affects D6220 before 1.0.0.40, D6400 before 1.0.0.74, D7000 before 1.0.1.60, D7800 before 1.0.1.34, D8500 before 1.0.3.39, DGN2200v4 before 1.0.0.94, DGN2200Bv4 before 1.0.0.94, EX6200v2 before 1.0.1.50, EX7000 before 1.0.0.56, JR6150 before 1.0.1.18, R6050 before 1.0.1.10J, R6100 before 1.0.1.16, R6150 before 1.0.1.10, R6220 before 1.1.0.50, R6250 before 1.0.4.12, R6300v2 before 1.0.4.12, R6400 before 1.0.1.24, R6400v2 before 1.0.2.32, R6700 before 1.0.1.26, R6700v2 before 1.2.0.4, R6800 before 1.0.1.10, R6900 before 1.0.1.26, R6900P before 1.0.0.58, R6900v2 before 1.2.0.4, R7000 before 1.0.9.6, R7000P before 1.0.0.58, R7100LG before 1.0.0.32, R7300 before 1.0.0.54, R7500 before 1.0.0.112, R7500v2 before 1.0.3.20, R7800 before 1.0.2.36, R7900 before 1.0.1.18, R8000 before 1.0.3.48, R8300 before 1.0.2.104, R8500 before 1.0.2.104, R9000 before 1.0.2.40, WNDR3400v3 before 1.0.1.14, WNDR3700v4 before 1.0.2.96, WNDR4300v1 before 1.0.2.98, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, and WNR3500Lv2 before 1.2.0.44.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 4.6 MEDIUM CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/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.

Physical

The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief (e.g., evil maid attack1) or persistent. An example of such an attack is a cold boot attack in which an attacker gains access to disk encryption keys after physically accessing the target system. Other examples include peripheral attacks via FireWire/USB Direct Memory Access (DMA).

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.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

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.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

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.0 4.6 MEDIUM CVSS:3.0/AC:L/AV:P/A:N/C:H/I:N/PR:N/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.

Physical

A vulnerability exploitable with Physical access requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief (e.g. evil maid attack [1]) or persistent. An example of such an attack is a cold boot attack which allows an attacker to access to disk encryption keys after gaining physical access to the system, or peripheral attacks such as Firewire/USB Direct Memory Access attacks.

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 against the vulnerable component.

Privileges Required

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

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a 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

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

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

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

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 that one has in the description of a vulnerability.

Environmental Metrics
V3.0 4.6 MEDIUM CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/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.

Physical

A vulnerability exploitable with Physical access requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief (e.g. evil maid attack [1]) or persistent. An example of such an attack is a cold boot attack which allows an attacker to access to disk encryption keys after gaining physical access to the system, or peripheral attacks such as Firewire/USB Direct Memory Access attacks.

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 against the vulnerable component.

Privileges Required

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

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a 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

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

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

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

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 that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 2.1 AV:L/AC:L/Au:N/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>>D6220_firmware >> Version To (excluding) 1.0.0.40

Netgear>>D6220 >> Version -

Configuraton 0

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

Netgear>>D6400 >> Version -

Configuraton 0

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

Netgear>>D7000 >> Version -

Configuraton 0

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

Netgear>>D7800 >> Version -

Configuraton 0

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

Netgear>>D8500 >> Version -

Configuraton 0

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

Netgear>>Dgn2200 >> Version v4

Configuraton 0

Netgear>>Dgn2200b_firmware >> Version To (excluding) 1.0.0.94

Netgear>>Dgn2200b >> Version v4

Configuraton 0

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

Netgear>>Ex6200 >> Version v2

Configuraton 0

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

Netgear>>Ex7000 >> Version -

Configuraton 0

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

Netgear>>Jr6150 >> Version -

Configuraton 0

Netgear>>R6050_firmware >> Version To (excluding) 1.0.1.10j

Netgear>>R6050 >> Version -

Configuraton 0

Netgear>>R6100_firmware >> Version To (excluding) 1.0.1.16

Netgear>>R6100 >> Version -

Configuraton 0

Netgear>>R6150_firmware >> Version To (excluding) 1.0.1.10

    Netgear>>R6150 >> Version -

    Configuraton 0

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

    Netgear>>R6220 >> Version -

    Configuraton 0

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

    Netgear>>R6250 >> Version -

    Configuraton 0

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

    Netgear>>R6300 >> Version v2

    Configuraton 0

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

    Netgear>>R6400 >> Version -

    Configuraton 0

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

    Netgear>>R6400 >> Version v2

    Configuraton 0

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

    Netgear>>R6700 >> Version -

    Configuraton 0

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

    Netgear>>R6700 >> Version v2

    Configuraton 0

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

    Netgear>>R6800 >> Version -

    Configuraton 0

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

    Netgear>>R6900 >> Version -

    Configuraton 0

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

    Netgear>>R6900p >> Version -

    Configuraton 0

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

    Netgear>>R6900 >> Version v2

    Configuraton 0

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

    Netgear>>R7000 >> Version -

    Configuraton 0

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

    Netgear>>R7000p >> Version -

    Configuraton 0

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

    Netgear>>R7100lg >> Version -

    Configuraton 0

    Netgear>>R7300_firmware >> Version To (excluding) 1.0.0.54

    Netgear>>R7300 >> Version -

    Configuraton 0

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

    Netgear>>R7500 >> Version -

    Configuraton 0

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

    Netgear>>R7500 >> Version v2

    Configuraton 0

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

    Netgear>>R7800 >> Version -

    Configuraton 0

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

    Netgear>>R7900 >> Version -

    Configuraton 0

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

    Netgear>>R8000 >> Version -

    Configuraton 0

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

    Netgear>>R8300 >> Version -

    Configuraton 0

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

    Netgear>>R8500 >> Version -

    Configuraton 0

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

    Netgear>>R9000 >> Version -

    Configuraton 0

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

    Netgear>>Wndr3400 >> Version v3

    Configuraton 0

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

    Netgear>>Wndr3700 >> Version v4

    Configuraton 0

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

    Netgear>>Wndr4300 >> Version v1

    Configuraton 0

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

    Netgear>>Wndr4300 >> Version v2

    Configuraton 0

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

    Netgear>>Wndr4500 >> Version v3

    Configuraton 0

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

    Netgear>>Wnr3500l >> Version v2

    References