Overview

Cryptographic keys may be embedded files such as configuration files or key files, certificate files, or other resource files bundled with the app, making them accessible to anyone who can extract the app's resources. Real-world cases include storing API keys, SSL/TLS private keys, or encryption keys within these files, which can lead to serious security vulnerabilities if the app is reverse-engineered.

Steps

  1. Use MASTG-TECH-0058 to extract the relevant binaries from app package.
  2. Use MASTG-TECH-0066 to look for the relevant APIs in the app binaries.

Observation

The output should include any instances where potential cryptographic keys are found hardcoded within the application's source code or binary.

Evaluation

The test case fails if hardcoded cryptographic keys are found within the source code or binary.

Further Validation Required:

Inspect each reported code location using MASTG-TECH-0076 to determine whether the identified data is indeed a cryptographic key used for security-relevant purposes: