CVE-2017-1723 : Détail

CVE-2017-1723

6.5
/
Moyen
Directory Traversal
A01-Broken Access Control
0.11%V3
Network
2018-04-26
14h00 +00:00
2024-09-17
02h42 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

IBM Security QRadar SIEM 7.2 and 7.3 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 134812.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 6.5 MEDIUM CVSS:3.0/AV:N/AC:L/PR:L/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.

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.

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 4 AV:N/AC:L/Au:S/C:P/I:N/A:N [email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Ibm>>Qradar_security_information_and_event_manager >> Version From (including) 7.2.0 To (excluding) 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.2.8

Ibm>>Qradar_security_information_and_event_manager >> Version 7.3.0

Ibm>>Qradar_security_information_and_event_manager >> Version 7.3.1

Ibm>>Qradar_security_information_and_event_manager >> Version 7.3.1

Ibm>>Qradar_security_information_and_event_manager >> Version 7.3.1

Configuraton 0

Ibm>>Qradar_incident_forensics >> Version From (including) 7.2.0 To (excluding) 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.2.8

Ibm>>Qradar_incident_forensics >> Version 7.3.0

Ibm>>Qradar_incident_forensics >> Version 7.3.1

Ibm>>Qradar_incident_forensics >> Version 7.3.1

Ibm>>Qradar_incident_forensics >> Version 7.3.1

Configuraton 0

Ibm>>Qradar_network_insights >> Version From (including) 7.2.0 To (excluding) 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.2.8

    Ibm>>Qradar_network_insights >> Version 7.3.0

    Ibm>>Qradar_network_insights >> Version 7.3.1

    Ibm>>Qradar_network_insights >> Version 7.3.1

    Ibm>>Qradar_network_insights >> Version 7.3.1

    Références