ID CVE-2008-3273
Summary JBoss Enterprise Application Platform (aka JBossEAP or EAP) before 4.2.0.CP03, and 4.3.0 before 4.3.0.CP01, allows remote attackers to obtain sensitive information about "deployed web contexts" via a request to the status servlet, as demonstrated by a full=true query string.
References
Vulnerable Configurations
  • cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp01
    cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp01
  • cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp02
    cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp02
  • cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp03
    cpe:2.3:a:jboss:enterprise_application_platform:4.2.0.cp03
  • cpe:2.3:a:jboss:enterprise_application_platform:4.3.0
    cpe:2.3:a:jboss:enterprise_application_platform:4.3.0
CVSS
Base: 5.0 (as of 11-08-2008 - 13:19)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
metasploit via4
description This module queries the JBoss status servlet to collect sensitive information, including URL paths, GET parameters and client IP addresses. This module has been tested against JBoss 4.0, 4.2.2 and 4.2.3.
id MSF:AUXILIARY/SCANNER/HTTP/JBOSS_STATUS
last seen 2019-03-11
modified 2018-09-15
published 2014-03-28
reliability Normal
reporter Rapid7
source https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/scanner/http/jboss_status.rb
title JBoss Status Servlet Information Gathering
nessus via4
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2008-0825.NASL
    description Updated JBoss Enterprise Application Platform (JBoss EAP) packages that resolve several security issues are now available for Red Hat Enterprise Linux 4. This update has been rated as having moderate security impact by the Red Hat Security Response Team. JBoss EAP is a middleware platform for Java 2 Platform, Enterprise Edition (J2EE) applications. JBoss Seam is a framework for building Java Internet applications by integrating the use of Asynchronous JavaScript and XML (AJAX), JavaServer Faces (JSF), Java Persistence (JPA), Enterprise Java Beans (EJB 3.0) and Business Process Management (BPM) technologies. This release of JBoss EAP for Red Hat Enterprise Linux 4 contains the JBoss Application Server and JBoss Seam. This release serves as a replacement for JBoss EAP 4.2.0.GA, and fixes the following security issues : These updated JBoss Enterprise Application Platform (JBoss EAP) packages resolve the following security issues : The JavaServer Faces (JSF) component was vulnerable to multiple cross-site scripting (XSS) vulnerabilities. An attacker could use these flaws to inject arbitrary web script or HTML. (CVE-2008-1285) Unauthenticated users were able to access the status servlet, which could allow remote attackers to acquire details about deployed web contexts. (CVE-2008-3273) These updated packages include bug fixes and enhancements in addition to the security fixes listed here. For the full list, refer to the JBoss EAP 4.2.0.CP03 release notes, linked to in the 'References' section of this advisory. Warning: before applying this update, please back up the JBoss EAP 'server//deploy/' directory, as well as any customized configuration files. Please note: some of the packages contained in this errata were available via the Red Hat Network prior to the release of this advisory. Users of JBoss Enterprise Application Platform (JBoss EAP) should upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 63860
    published 2013-01-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63860
    title RHEL 4 : JBoss EAP (RHSA-2008:0825)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2008-0826.NASL
    description Updated JBoss Enterprise Application Platform (JBoss EAP) packages that fix various security issues are now available for Red Hat Enterprise Linux 4. This update has been rated as having moderate security impact by the Red Hat Security Response Team. JBoss EAP is a middleware platform for Java 2 Platform, Enterprise Edition (J2EE) applications. This release of JBoss EAP for Red Hat Enterprise Linux 4 contains the JBoss Application Server and JBoss Seam. This release serves as a replacement for JBoss EAP 4.3.0.GA, and fixes the following security issues : The JavaServer Faces (JSF) component was vulnerable to multiple cross-site scripting (XSS) vulnerabilities. An attacker could use these flaws to inject arbitrary web script or HTML. (CVE-2008-1285) Unauthenticated users were able to access the status servlet, which could allow remote attackers to acquire details about deployed web contexts. (CVE-2008-3273) These updated packages include bug fixes and enhancements which are not listed here. For a full list, refer to the JBoss EAP 4.3.0.CP01 release notes, linked to in the 'References' section of this advisory. Warning: before applying this update, please back up the JBoss EAP 'server/[configuration]/deploy/' directory, and any customized configuration files. Please note: some of the packages contained in this errata were available via the Red Hat Network prior to the release of this advisory. All users of JBoss EAP on Red Hat Enterprise Linux 4 are advised to upgrade to these updated packages, which resolve these issues.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 63861
    published 2013-01-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63861
    title RHEL 4 : JBoss EAP (RHSA-2008:0826)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2008-0828.NASL
    description Updated JBoss Enterprise Application Platform (JBoss EAP) packages that fix various security issues are now available for Red Hat Enterprise Linux 5. This update has been rated as having moderate security impact by the Red Hat Security Response Team. JBoss EAP is a middleware platform for Java 2 Platform, Enterprise Edition (J2EE) applications. This release of JBoss EAP for Red Hat Enterprise Linux 5 contains the JBoss Application Server and JBoss Seam. This release serves as a replacement to JBoss EAP 4.3.0.GA, and fixes the following security issues : The JavaServer Faces (JSF) component was vulnerable to multiple cross-site scripting (XSS) vulnerabilities. An attacker could use these flaws to inject arbitrary web script or HTML. (CVE-2008-1285) Unauthenticated users were able to access the status servlet, which could allow remote attackers to acquire details about deployed web contexts. (CVE-2008-3273) These updated packages include bug fixes and enhancements which are not listed here. For a full list, refer to the JBoss EAP 4.3.0.CP01 release notes, linked to in the 'References' section of this advisory. Warning: before applying this update, please back up the JBoss EAP 'server/[configuration]/deploy/' directory, and any customized configuration files. All users of JBoss EAP on Red Hat Enterprise Linux 5 are advised to upgrade to these updated packages, which resolve these issues.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 63863
    published 2013-01-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63863
    title RHEL 5 : JBoss EAP (RHSA-2008:0828)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2008-0827.NASL
    description Updated JBoss Enterprise Application Platform (JBoss EAP) packages that resolve several security issues are now available for Red Hat Enterprise Linux 5. This update has been rated as having moderate security impact by the Red Hat Security Response Team. JBoss EAP is a middleware platform for Java 2 Platform, Enterprise Edition (J2EE) applications. JBoss Seam is a framework for building Java Internet applications by integrating the use of Asynchronous JavaScript and XML (AJAX), JavaServer Faces (JSF), Java Persistence (JPA), Enterprise Java Beans (EJB 3.0) and Business Process Management (BPM) technologies. This release of JBoss EAP for Red Hat Enterprise Linux 5 contains the JBoss Application Server and JBoss Seam. This release serves as a replacement for JBoss EAP 4.2.0.GA, and fixes the following security issues : These updated JBoss Enterprise Application Platform (JBoss EAP) packages resolve the following security issues : The JavaServer Faces (JSF) component was vulnerable to multiple cross-site scripting (XSS) vulnerabilities. An attacker could use these flaws to inject arbitrary web script or HTML. (CVE-2008-1285) Unauthenticated users were able to access the status servlet, which could allow remote attackers to acquire details about deployed web contexts. (CVE-2008-3273) These updated packages include bug fixes and enhancements in addition to the security fixes listed here. For the full list, refer to the JBoss EAP 4.2.0.CP03 release notes, linked to in the 'References' section of this advisory. Warning: before applying this update, please back up the JBoss EAP 'server//deploy/' directory, as well as any customized configuration files. Users of JBoss Enterprise Application Platform (JBoss EAP) should upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 63862
    published 2013-01-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63862
    title RHEL 5 : JBoss EAP (RHSA-2008:0827)
  • NASL family CGI abuses
    NASL id JBOSS_EAP_INFO_DISCLOSURE_VULN.NASL
    description The version of JBoss Enterprise Application Platform (EAP) running on the remote host allows unauthenticated access to a status servlet, which is used to monitor sessions and requests sent to the server. This vulnerability (CVE-2008-3273) was fixed in versions 4.2.0.CP03 and 4.3.0.CP01, but was later re-introduced (CVE-2010-1429) by an unrelated bug fix.
    last seen 2019-02-21
    modified 2018-06-13
    plugin id 33869
    published 2008-08-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=33869
    title JBoss Enterprise Application Platform (EAP) Status Servlet Request Remote Information Disclosure
redhat via4
advisories
  • rhsa
    id RHSA-2008:0825
  • rhsa
    id RHSA-2008:0826
  • rhsa
    id RHSA-2008:0827
  • rhsa
    id RHSA-2008:0828
refmap via4
bid 30540
confirm
hp
  • HPSBMU02736
  • SSRT100699
sectrack 1020628
xf jbosseap-statusservlet-info-disclosure(44235)
Last major update 05-11-2012 - 23:05
Published 10-08-2008 - 16:41
Last modified 07-08-2017 - 21:31
Back to Top