[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SYMSA-2006-011: JBoss Java Class DeploymentFileRepository Directory Traversal
-----BEGIN PGP SIGNED MESSAGE-----
Symantec Vulnerability Research
Advisory ID: SYMSA-2006-011
Advisory Title: JBoss Java Class DeploymentFileRepository Directory Traversal
Author: Oliver Karow / olver_Karow[@]symantec.com
Release Date: 27-11-2006
Application: JBoss Web Server 1.0.0.GA
Platform: Java (Windows / Linux)
Severity: Remotely exploitable / User access
Vendor status: Vendor verified, patch is available
CVE Number: CVE-2006-5750
From JBoss Documentation:
"This class wraps the file system for deployments. It gives a
file-based persistence mechanism for deployments. Used by
web-console to store -service.xml files, -ds.xml files, etc...,
really anything text based. Deployments are tied to a specific
name and that name corresponds to the base file name."
The class can be abused to create files outside of the application
root directory, and could allow an attacker who has access to
the management console the ability to read or write files with
the permissions of the JBoss user, potentially leading to
arbitrary code execution.
The method setBaseDir() of the class
org.jboss.console.manager.DeploymentFileRepository does not
check if the basedir is set to a directory outside of the application
root directory via directory traversal. In conjunction with
the usage of the methods store() and remove(), it is possible
to create and delete arbitrary files on the target system.
The class is used by JBoss Web Server's web-console/jmx-console
which by default is accessible from remote by unauthenticated
users. During our research, it was possible to create and
execute JSP-Files and to overwrite configuration files.
The class may also be used by other JBoss Applications, thus
making them vulnerable to the same attacks.
Due to JBoss Web Server's missing default authentication
enforcement, complete control of the application is also possible.
Red Hat has verified the flaw in the DeploymentFileRepository class
of the JBoss application server. A remote attacker who is able to
access the console manager could read or write to files with the
permissions of the JBoss user. This could potentially lead to
arbitrary code execution as the JBoss user (CVE-2006-5750).
Please note that the JBoss console manager should always be secured
prior to deployment. By default, the JBoss installer gives users the
ability to password protect the console manager, limiting an attack
using this vulnerability to authorised users. These steps can also
be performed manually.
This issue affected the JBoss Application Server. A patch for this
issue is available:
This issue affected Red Hat Application Stack. An updated jbossas
package to correct this issue is available along with our advisory:
Common Vulnerabilities and Exposures (CVE) Information:
The Common Vulnerabilities and Exposures (CVE) project has assigned
the following names to these issues. These are candidates for
inclusion in the CVE list (http://cve.mitre.org), which standardizes
names for security problems.
- -------Symantec Vulnerability Research Advisory Information-------
For questions about this advisory, or to report an error:
For details on Symantec's Vulnerability Reporting Policy:
Symantec Vulnerability Research Advisory Archive:
Symantec Vulnerability Research GPG Key:
- -------------Symantec Product Advisory Information-------------
To Report a Security Vulnerability in a Symantec Product:
For general information on Symantec's Product Vulnerability
reporting and response:
Symantec Product Advisory Archive:
Symantec Product Advisory PGP Key:
Copyright (c) 2006 by Symantec Corp.
Permission to redistribute this alert electronically is granted
as long as it is not edited in any way unless authorized by
Symantec Consulting Services. Reprinting the whole or part of
this alert in any medium other than electronically requires
permission from cs_advisories@xxxxxxxxxxxxx
The information in the advisory is believed to be accurate at the
time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS
condition. There are no warranties with regard to this information.
Neither the author nor the publisher accepts any liability for any
direct, indirect, or consequential loss or damage arising from use
of, or reliance on, this information.
Symantec, Symantec products, and Symantec Consulting Services are
registered trademarks of Symantec Corp. and/or affiliated companies
in the United States and other countries. All other registered and
unregistered trademarks represented in this document are the sole
property of their respective companies/owners.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v18.104.22.168 (GNU/Linux)
-----END PGP SIGNATURE-----