CVE-2018-0059 : 상세 정보

CVE-2018-0059

5.4
/
보통
0.13%V4
2018-10-10
18h00 +00:00
Cross-site Scripting
A03-Injection
Network
2024-09-16
18h24 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

ScreenOS: Stored Cross-Site Scripting (XSS) vulnerability

A persistent cross-site scripting vulnerability in the graphical user interface of ScreenOS may allow a remote authenticated user to inject web script or HTML and steal sensitive data and credentials from a web administration session, possibly tricking a follow-on administrative user to perform administrative actions on the device. Affected releases are Juniper Networks ScreenOS 6.3.0 versions prior to 6.3.0r26.

CVE 해결 방법

The following software releases have been updated to resolve this specific issue: ScreenOS 6.3.0r26 and all subsequent releases. Review and clear any previously stored cross-site scripting entries.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-79 Improper Neutralization of Input During Web Page Generation
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.0 5.4 MEDIUM CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from 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 against the vulnerable component.

Privileges Required

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

Low

The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

User Interaction

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

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

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.

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 constrained. 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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on 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

V2 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N nvd@nist.gov

EPSS

EPSS는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.

EPSS 점수

EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.

EPSS 백분위수

백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.

언급된 제품

구성 0

Juniper>>Netscreen_screenos >> Version 6.3.0

Juniper>>Netscreen_screenos >> Version 6.3.0r1

Juniper>>Netscreen_screenos >> Version 6.3.0r2

Juniper>>Netscreen_screenos >> Version 6.3.0r3

Juniper>>Netscreen_screenos >> Version 6.3.0r4

Juniper>>Netscreen_screenos >> Version 6.3.0r5

Juniper>>Netscreen_screenos >> Version 6.3.0r6

Juniper>>Netscreen_screenos >> Version 6.3.0r7

Juniper>>Netscreen_screenos >> Version 6.3.0r8

Juniper>>Netscreen_screenos >> Version 6.3.0r9

Juniper>>Netscreen_screenos >> Version 6.3.0r10

Juniper>>Netscreen_screenos >> Version 6.3.0r11

Juniper>>Netscreen_screenos >> Version 6.3.0r12

Juniper>>Netscreen_screenos >> Version 6.3.0r13

Juniper>>Netscreen_screenos >> Version 6.3.0r14

Juniper>>Netscreen_screenos >> Version 6.3.0r15

Juniper>>Netscreen_screenos >> Version 6.3.0r16

Juniper>>Netscreen_screenos >> Version 6.3.0r17

Juniper>>Netscreen_screenos >> Version 6.3.0r18

Juniper>>Netscreen_screenos >> Version 6.3.0r19

Juniper>>Netscreen_screenos >> Version 6.3.0r21

Juniper>>Netscreen_screenos >> Version 6.3.0r22

Juniper>>Netscreen_screenos >> Version 6.3.0r23

Juniper>>Netscreen_screenos >> Version 6.3.0r23b1

Juniper>>Netscreen_screenos >> Version 6.3.0r24

Juniper>>Netscreen_screenos >> Version 6.3.0r24b1

Juniper>>Netscreen_screenos >> Version 6.3.0r25

참고 자료

https://kb.juniper.net/JSA10894
Tags : x_refsource_CONFIRM