Vulnerabilities > CVE-2016-0710 - SQL Injection vulnerability in Apache Jetspeed

047910
CVSS 8.8 - HIGH
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
LOW
Confidentiality impact
HIGH
Integrity impact
HIGH
Availability impact
HIGH
network
low complexity
apache
CWE-89
nessus
exploit available
metasploit

Summary

Multiple SQL injection vulnerabilities in the User Manager service in Apache Jetspeed before 2.3.1 allow remote attackers to execute arbitrary SQL commands via the (1) role or (2) user parameter to services/usermanager/users/.

Vulnerable Configurations

Part Description Count
Application
Apache
4

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:

Exploit-Db

descriptionApache Jetspeed Arbitrary File Upload. CVE-2016-0709,CVE-2016-0710. Remote exploit for java platform
fileexploits/java/remote/39643.rb
idEDB-ID:39643
last seen2016-03-31
modified2016-03-31
platformjava
port8080
published2016-03-31
reportermetasploit
sourcehttps://www.exploit-db.com/download/39643/
titleApache Jetspeed Arbitrary File Upload
typeremote

Metasploit

descriptionThis module exploits the unsecured User Manager REST API and a ZIP file path traversal in Apache Jetspeed-2, version 2.3.0 and unknown earlier versions, to upload and execute a shell. Note: this exploit will create, use, and then delete a new admin user. Warning: in testing, exploiting the file upload clobbered the web interface beyond repair. No workaround has been found yet. Use this module at your own risk. No check will be implemented.
idMSF:EXPLOIT/MULTI/HTTP/APACHE_JETSPEED_FILE_UPLOAD
last seen2020-06-10
modified2019-02-25
published2016-03-15
references
reporterRapid7
sourcehttps://github.com/rapid7/metasploit-framework/blob/master//modules/exploits/multi/http/apache_jetspeed_file_upload.rb
titleApache Jetspeed Arbitrary File Upload

Nessus

NASL familyCGI abuses
NASL idAPACHE_JETSPEED_USERMANAGER_SQLI.NASL
descriptionThe Apache Jetspeed application running on the remote host is affected by a SQL injection vulnerability in the User Manager service due to improper sanitization of user-supplied input to the
last seen2020-06-01
modified2020-06-02
plugin id90248
published2016-03-28
reporterThis script is Copyright (C) 2016-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
sourcehttps://www.tenable.com/plugins/nessus/90248
titleApache Jetspeed User Manager Service SQLi

Packetstorm

data sourcehttps://packetstormsecurity.com/files/download/136489/apache_jetspeed_file_upload.rb.txt
idPACKETSTORM:136489
last seen2016-12-05
published2016-03-31
reporterwvu
sourcehttps://packetstormsecurity.com/files/136489/Apache-Jetspeed-Arbitrary-File-Upload.html
titleApache Jetspeed Arbitrary File Upload

Seebug

bulletinFamilyexploit
description通过管理员账号在后台 Portal Site Manger 处 import 恶意构造的 ZIP 文件,ZIP 压缩文件中包含名称为 ../../webapps/de.jsp 的文件,在后台处理 上传时会拼接此文件名导致目录穿越,控制文件上传路径。 ![](https://images.seebug.org/1457337295104) poc.zip 包 含 名 为 ../../webapps/ROOT/de.jsp 的 文 件 , 内 容 为 is vulnerable: ![](https://images.seebug.org/1457337309111) 上传后,即可在网站根目录(根据目标环境决定)访问到 de.jsp 文件: ![](https://images.seebug.org/1457337322130) 要利用目录穿越上传任意文件虽然需要管理权限的账户,但是通过前一个漏 洞可以轻松创建一个拥有管理者权限的任意账户,再利用此漏洞上传 Webshel l 来控制目标机器。 ### 关联漏洞 * [CVE-2016-0710 Apache Jetspeed 用户管理 REST API 未授权访问漏洞](https://www.seebug.org/vuldb/ssvid-90922) ### 参考链接 [1] http://haxx.ml/post/140552592371/remote-code-execution-in-apac he-jetspeed-230-and [2] https://portals.apache.org/jetspeed-2/security-reports.html
idSSV:90920
last seen2017-11-19
modified2016-03-07
published2016-03-07
reporterRoot
titleApache Jetspeed 目录穿越漏洞