| Summary: | [Webapp] Stack trace displayed in help system for incorrect nav param value | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | steilhet |
| Component: | User Assistance | Assignee: | Chris Goldthorpe <cgold> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cgold, steilhet |
| Version: | 4.2 | ||
| Target Milestone: | 3.8 M3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
steilhet
I don't see this as a security risk since the lines all come from open source software but I agree that it does not look good from the users perspective and it would be better to display an error page. Actually, this is one of the OWASP top 10 issues "A6-Security Misconfiguration". (https://www.owasp.org/index.php/Top_10_2010-A6). From their site: "Scenario #4: App server configuration allows stack traces to be returned to users, potentially exposing underlying flaws. Attackers love the extra information error messages provide." Also see: https://www.owasp.org/index.php/Error_Handling The idea is that you don't want to give away any information to an attacker such as: - Language used - Frameworks used - Technology used - What the exact error is (null pointer in this case) - file names - directory names - 3rd party components used Any of this can be used by an attacker to hone their attack not just on the help system, but possibly on other components of the system as well. In this case the security research team believes that this particular bug is a low risk potential vulnerability, however, they do believe that it needs to be fixed in order to ensure that it is never used by an attacker in any way to gain extra knowledge about the system. A fix has been committed to master with commit message: Bug 359579 - [Webapp] Stack trace displayed in help system for incorrect nav param value |