237 – Technical information leak - Print Functions
Description
Technical information is obtained from the application due to the use of print functions (Print, PrinStackTrace, Println, among others) whose outputs are normally shown in the stdout (standard output). In development environment it is acceptable to use these functions to see errors (Debug), but using them in production environment is the same as exposing yourself to show sensitive information of the application.
Impact
- Enlarge attack surface. - Access to technical information of the application.
Recommendation
The application must securely report all possible events that may occur, it must not provide technical or sensitive information to unauthorized users, as they could exploit it to extend the knowledge of the attack surface.
Threat
Authenticated local attacker with access to the server console.
Expected Remediation Time
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: L
- Attack complexity: L
- Attack Requirements: N
- Privileges required: H
- User interaction: N
- Confidentiality (VC): L
- Integrity (VI): N
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: P