CVE-2016-7065 : Detail

CVE-2016-7065

8.8
/
High
A08-Soft and Data Integrity Fail
0.65%V3
Network
2016-10-13
12h00 +00:00
2016-12-21
20h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

The JMX servlet in Red Hat JBoss Enterprise Application Platform (EAP) 4 and 5 allows remote authenticated users to cause a denial of service and possibly execute arbitrary code via a crafted serialized Java object.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-502 Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 8.8 HIGH CVSS:3.0/AV:N/AC:L/PR:L/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.

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.

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 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P nvd@nist.gov

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.

Exploit information

Exploit Database EDB-ID : 40842

Publication date : 2016-11-27 23h00 +00:00
Author : Mediaservice.net Srl.
EDB Verified : Yes

Security Advisory @ Mediaservice.net Srl (#05, 23/11/2016) Data Security Division Title: Red Hat JBoss EAP deserialization of untrusted data Application: JBoss EAP 5.2.X and prior versions Description: The application server deserializes untrusted data via the JMX Invoker Servlet. This can lead to a DoS via resource exhaustion and potentially remote code execution. Author: Federico Dotta <federico.dotta@mediaservice.net> Maurizio Agazzini <inode@mediaservice.net> Vendor Status: Will not fix CVE Candidate: The Common Vulnerabilities and Exposures project has assigned the name CVE-2016-7065 to this issue. References: http://lab.mediaservice.net/advisory/2016-05-jboss.txt http://lab.mediaservice.net/code/jboss_payload.zip https://bugzilla.redhat.com/show_bug.cgi?id=1382534 1. Abstract. JBoss EAP's JMX Invoker Servlet is exposed by default on port 8080/TCP. The communication employs serialized Java objects, encapsulated in HTTP requests and responses. The server deserializes these objects without checking the object type. This behavior can be exploited to cause a denial of service and potentially execute arbitrary code. The objects that can cause the DoS are based on known disclosed payloads taken from: - https://gist.github.com/coekie/a27cc406fc9f3dc7a70d Currently there is no known chain that allows code execution on JBoss EAP, however new chains are discovered every day. 2. Example Attack Session. Submit an authenticated POST request to the JMX Invoker Servlet URL (for example: http://localhost:8080/invoker/JMXInvokerServlet) with one of the following objects in the body of the request: * 01_BigString_limited.ser: it's a string object; the server will reply in a normal way (object size similar to the next one). * 02_SerialDOS_limited.ser: the application server will require about 2 minutes to execute the request with 100% CPU usage. * 03_BigString.ser: it's a string object; the server will reply in a normal way (object size similar to the next one). * 04_SerialDOS.ser: the application server will require an unknown amount of time to execute the request with 100% CPU usage. 3. Affected Platforms. This vulnerability affects versions 4 and 5 of JBoss EAP. 4. Fix. Red Hat will not fix the issue because JBoss EAP 4 is out of maintenance support and JBoss EAP 5 is close to the end of its maintenance period. 5. Proof Of Concept. See jboss_payload.zip (40842.zip) and Example Attack Session above. http://lab.mediaservice.net/code/jboss_payload.zip https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/40842.zip 6. Timeline 06/10/2016 - First communication sent to Red Hat Security Response Team 07/10/2016 - Red Hat Security Response Team response, Bug 1382534 23/11/2016 - Security Advisory released Copyright (c) 2016 @ Mediaservice.net Srl. All rights reserved. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/40842.zip

Products Mentioned

Configuraton 0

Redhat>>Jboss_enterprise_application_platform >> Version 4.0.0

Redhat>>Jboss_enterprise_application_platform >> Version 5.0.0

References

https://www.exploit-db.com/exploits/40842/
Tags : exploit, x_refsource_EXPLOIT-DB
http://seclists.org/fulldisclosure/2016/Nov/143
Tags : mailing-list, x_refsource_FULLDISC
http://www.securityfocus.com/bid/93462
Tags : vdb-entry, x_refsource_BID