The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.
N/A
Threat Mapped score: 0.0
Industry: Finiancial
Threat priority: Unclassified
CVE: CVE-2004-1581
chain: product does not protect against direct request of an include file, leading to resultant path disclosure when the include file does not successfully execute.
CVE: CVE-2004-1579
Single "'" inserted into SQL query leads to invalid SQL query execution, triggering full path disclosure. Possibly resultant from more general SQL injection issue.
CVE: CVE-2005-0459
chain: product does not protect against direct request of a library file, leading to resultant path disclosure when the file does not successfully execute.
CVE: CVE-2005-0443
invalid parameter triggers a failure to find an include file, leading to infoleak in error message.
CVE: CVE-2005-0433
Various invalid requests lead to information leak in verbose error messages describing the failure to instantiate a class, open a configuration file, or execute an undefined function.
CVE: CVE-2004-1101
Improper handling of filename request with trailing "/" causes multiple consequences, including information leak in Visual Basic error message.
N/A
N/A
| Phase | Note |
|---|---|
| Architecture and Design | PHP applications are often targeted for having this issue when the PHP interpreter generates the error outside of the application's control. However, other languages/environments exhibit the same issue. |
| Implementation | REALIZATION: This weakness is caused during implementation of an architectural security tactic. |
| Operation | N/A |
Intro: The following servlet code does not catch runtime exceptions, meaning that if such an exception were to occur, the container may display potentially dangerous information (such as a full stack trace).
public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String username = request.getParameter("username"); // May cause unchecked NullPointerException. if (username.length() < 10) { ... } }Intro: In the following Java example the class InputFileRead enables an input file to be read using a FileReader object. In the constructor of this class a default input file path is set to some directory on the local file system and the method setInputFile must be called to set the name of the input file to be read in the default directory. The method readInputFile will create the FileReader object and will read the contents of the file. If the method setInputFile is not called prior to calling the method readInputFile then the File object will remain null when initializing the FileReader object. A Java RuntimeException will be raised, and an error message will be output to the user.
Body: However, the error message output to the user contains information regarding the default directory on the local file system. This information can be exploited and may lead to unauthorized access or use of the system. Any Java RuntimeExceptions that are handled should not expose sensitive information to the user.
public class InputFileRead { private File readFile = null; private FileReader reader = null; private String inputFilePath = null; private final String DEFAULT_FILE_PATH = "c:\\somedirectory\\"; public InputFileRead() { inputFilePath = DEFAULT_FILE_PATH; } public void setInputFile(String inputFile) { /* Assume appropriate validation / encoding is used and privileges / permissions are preserved */ } public void readInputFile() { try { reader = new FileReader(readFile); ... } catch (RuntimeException rex) { System.err.println("Error: Cannot open input file in the directory " + inputFilePath); System.err.println("Input file has not been set, call setInputFile method before calling readInputFile"); } catch (FileNotFoundException ex) {...} } }