CVE-2017-12615 : Detail

CVE-2017-12615

8.1
/
High
File Inclusion
A04-Insecure Design
96.55%V3
Network
2017-09-19
13h00 +00:00
2025-02-06
21h00 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-434 Unrestricted Upload of File with Dangerous Type
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 8.1 HIGH CVSS:3.1/AV:N/AC:H/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

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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 of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human 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

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

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 a 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 a 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 in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P [email protected]

CISA KEV (Known Exploited Vulnerabilities)

Vulnerability name : Apache Tomcat on Windows Remote Code Execution Vulnerability

Required action : Apply updates per vendor instructions.

Known To Be Used in Ransomware Campaigns : Known

Added : 2022-03-24 23h00 +00:00

Action is due : 2022-04-14 22h00 +00:00

Important information
This CVE is identified as vulnerable and poses an active threat, according to the Catalog of Known Exploited Vulnerabilities (CISA KEV). The CISA has listed this vulnerability as actively exploited by cybercriminals, emphasizing the importance of taking immediate action to address this flaw. It is imperative to prioritize the update and remediation of this CVE to protect systems against potential cyberattacks.

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.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 42953

Publication date : 2017-09-19 22h00 +00:00
Author : xxlegend
EDB Verified : No

# E-DB Note: https://www.alphabot.com/security/blog/2017/java/Apache-Tomcat-RCE-CVE-2017-12617.html When running on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server. The PoC is like this: PUT /1.jsp/ HTTP/1.1 Host: 192.168.3.103:8080 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8 Referer: http://192.168.3.103:8080/examples/ Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.8,zh-CN;q=0.6,zh;q=0.4,zh-TW;q=0.2 Cookie: JSESSIONID=A27674F21B3308B4D893205FD2E2BF94 Connection: close Content-Length: 26 <% out.println("hello");%> It is the bypass for CVE-2017-12615

Products Mentioned

Configuraton 0

Apache>>Tomcat >> Version From (including) 7.0.0 To (including) 7.0.79

Microsoft>>Windows >> Version -

Configuraton 0

Netapp>>7-mode_transition_tool >> Version -

Netapp>>Oncommand_balance >> Version -

Netapp>>Oncommand_shift >> Version -

Configuraton 0

Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 7.4

    Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 7.6

    • Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 7.6 (Open CPE detail)

    Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 7.7

    • Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 7.7 (Open CPE detail)

    Redhat>>Jboss_enterprise_web_server >> Version 2.0.0

    Redhat>>Jboss_enterprise_web_server >> Version 3.0.0

    Redhat>>Jboss_enterprise_web_server_text-only_advisories >> Version -

      Redhat>>Enterprise_linux_desktop >> Version 6.0

      Redhat>>Enterprise_linux_desktop >> Version 7.0

      Redhat>>Enterprise_linux_eus >> Version 7.4

      Redhat>>Enterprise_linux_eus >> Version 7.5

      Redhat>>Enterprise_linux_eus >> Version 7.6

      Redhat>>Enterprise_linux_eus >> Version 7.7

      Redhat>>Enterprise_linux_eus_compute_node >> Version 7.4

      Redhat>>Enterprise_linux_eus_compute_node >> Version 7.5

      Redhat>>Enterprise_linux_eus_compute_node >> Version 7.6

      Redhat>>Enterprise_linux_eus_compute_node >> Version 7.7

      Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 7.0_s390x

      Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 7.4_s390x

      Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 7.5_s390x

      Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 7.6_s390x

      Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 7.7_s390x

      Redhat>>Enterprise_linux_for_power_big_endian >> Version 7.0_ppc64

      Redhat>>Enterprise_linux_for_power_big_endian_eus >> Version 7.4_ppc64

      Redhat>>Enterprise_linux_for_power_big_endian_eus >> Version 7.5_ppc64

      Redhat>>Enterprise_linux_for_power_big_endian_eus >> Version 7.6_ppc64

      Redhat>>Enterprise_linux_for_power_big_endian_eus >> Version 7.7_ppc64

      Redhat>>Enterprise_linux_for_power_little_endian >> Version 7.0_ppc64le

      Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.4_ppc64le

      • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.4_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.5_ppc64le

      • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.5_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.6_ppc64le

      • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.6_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.7_ppc64le

      • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 7.7_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_for_scientific_computing >> Version 7.0

      Redhat>>Enterprise_linux_server >> Version 6.0

      Redhat>>Enterprise_linux_server >> Version 7.0

      Redhat>>Enterprise_linux_server_aus >> Version 7.4

      Redhat>>Enterprise_linux_server_aus >> Version 7.6

      Redhat>>Enterprise_linux_server_aus >> Version 7.7

      Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.4_ppc64le

      • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.4_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.6_ppc64le

      • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.6_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.7_ppc64le

      • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 7.7_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.2_ppc64le

      • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.2_ppc64le (Open CPE detail)

      Redhat>>Enterprise_linux_server_tus >> Version 7.4

      Redhat>>Enterprise_linux_server_tus >> Version 7.6

      Redhat>>Enterprise_linux_server_tus >> Version 7.7

      Redhat>>Enterprise_linux_workstation >> Version 6.0

      Redhat>>Enterprise_linux_workstation >> Version 7.0

      References

      https://access.redhat.com/errata/RHSA-2017:3113
      Tags : vendor-advisory, x_refsource_REDHAT
      https://access.redhat.com/errata/RHSA-2017:3080
      Tags : vendor-advisory, x_refsource_REDHAT
      http://www.securitytracker.com/id/1039392
      Tags : vdb-entry, x_refsource_SECTRACK
      https://access.redhat.com/errata/RHSA-2018:0465
      Tags : vendor-advisory, x_refsource_REDHAT
      https://access.redhat.com/errata/RHSA-2017:3114
      Tags : vendor-advisory, x_refsource_REDHAT
      http://www.securityfocus.com/bid/100901
      Tags : vdb-entry, x_refsource_BID
      https://access.redhat.com/errata/RHSA-2018:0466
      Tags : vendor-advisory, x_refsource_REDHAT
      https://www.exploit-db.com/exploits/42953/
      Tags : exploit, x_refsource_EXPLOIT-DB
      https://access.redhat.com/errata/RHSA-2017:3081
      Tags : vendor-advisory, x_refsource_REDHAT