You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Client logged an issue via admin about potential security risk, because of using printStackTrace in the application source code.
I am attaching the full test report.
===================================
Abstract:
It is observed that the application was using printStackTrace in the application source code. A stack trace is generated whenever application crashes because of an error or an exception.
Impact:
Display stack trace to end-user might introduce a potential security risk as stack trace shows a list of method calls that lead to the exception being thrown, together with the filenames and line numbers where the calls happened. This information may enable attacker to target known vulnerabilities of the components.
Ease of Exploitation:
Difficult
Recommendation:
It is recommended to restrict use of printStackTrace() throughout the application.
===================================
Also the client found that one of the places, where printStackTrace is used, is in RuntimeHelper.java.
t.1406435
The text was updated successfully, but these errors were encountered:
A Client logged an issue via admin about potential security risk, because of using
printStackTrace
in the application source code.I am attaching the full test report.
Also the client found that one of the places, where
printStackTrace
is used, is in RuntimeHelper.java.t.1406435
The text was updated successfully, but these errors were encountered: