bugtraq - MRO Maximo v4 & v5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: 5 May 2005 11:03:37 -0000
From: Felix <felix.shnir@....com>
To: bugtraq@...urityfocus.com
Subject: MRO Maximo v4 & v5

Due to the fact that all of the files for Maximo Self Service application are served from one directory (maximo_installation) by the integrated Tomcat server, the files not recognized by Tomcat as needing to be run (*.jsps or mapped servlets) are not protected.  Therefore, if one was to call upon a known Maximo file name (such as MXServer.properties, they would receive the file just like a request for download from any other web server.  This means that everything under the maximo_install directory are semi-open to the public.  This includes stored passwords and database locations in these files.