Security controls bypass or absence - Debug Protection
Description
Debug controls protection do not span the wide variety of use models from internal hardware debug through debug of performance issues of software running. The application is deployed to unauthorized actors with debugging code still enabled or active.
Impact
- Create unintended entry points or expose sensitive information.
- Start a successful remote debugging session and is likely to disclose confidential information about the web application and supporting infrastructure.
Recommendation
- Assign debug programs user right only to administrators or trusted users to reduce the risk of this potential vulnerability.
- Remove debug code before deploying the application.
Threat
An attacker access to the application and can debug it, will be able to get sensitive information stored in a device.
Expected Remediation Time
⌚ 450 minutes.
Score
Default score using CVSS 3.1. It may change depending on the context of the src.
Base
- Attack vector: P
- Attack complexity: L
- Privileges required: N
- User interaction: N
- Scope: U
- Confidentiality: L
- Integrity: N
- Availability: N
Temporal
- Exploit code maturity: X
- Remediation level: X
- Report confidence: X
Result
- Vector string: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:X
- Score:
- Base: 2.4
- Temporal: 2.4
- Severity:
- Base: Low
- Temporal: Low
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: P
- Attack complexity: L
- Attack Requirements: N
- Privileges required: N
- 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: X
Result 4.0
- Vector string: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X
- Score:
- CVSS-BT: 2.4
- Severity:
- CVSS-BT: Low
Compliant code
There are no debugging functions present in the source code
public class myClass {
public static void main(String[] args) {
try {
//Code to do something
} catch (Exception e) {
//Handle exception
}
}
}
Non compliant code
Debug functions like printStackTrace are present in production code
public class myClass {
public static void main(String[] args) {
try {
//Code to do something
System.out.println(result);
} catch (Exception e) {
e.printStackTrace();
}
}
}
Details
https://mobile-security.gitbook.io/mobile-security-testing-guide/android-testing-guide/0x05j-testing-resiliency-against-reverse-engineering#owasp-masvs
Requirements
Fixes
