Reported by Symantec: 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. 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.
Removing embargo. See also http://kbase.redhat.com/faq/FAQ_107_9629.shtm
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0743.html