Skip to main content

Security controls bypass or absence - Anti hooking

Description

The application does not have anti-hooking protections, allowing tools such as Frida to work in its execution.

Impact

  • Evade security controls such as SSL pinning.
  • Intercept function calls and messages to alter the behavior of the application.

Recommendation

Enabling anti-hooking controls in the application.

Threat

Anonymous attcker from the Internet.

Expected Remediation Time

⌚ 300 minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base

  • Attack vector: N
  • Attack complexity: L
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: L
  • Integrity: L
  • Availability: N

Temporal

  • Exploit code madurity: X
  • Remediation level: O
  • Report confidence: X

Result

  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:X
  • Score:
    • Base: 6.5
    • Temporal: 6.2
  • Severity:
    • Base: Medium
    • Temporal: Medium

Code Examples

Compliant code

The application should implement several methods to detect non native files

try {
//Code to detect external hooks/files or non native files or procedures
throw new Exception("Deteck hook");
} catch (Exception e) {
Log.Careful("HookDetection", e.toString());
}

Non compliant code

There are no specific protection methods in the application to detect external hooks and stop the runtime

Requirements