Skip to main content

Insufficient data authenticity validation - APK signing

Description​

The APK is not digitally signed.

Impact​

Mischief users into installing an APK that is not owned by the original author.

Recommendation​

Digitally sign the APK.

Threat​

Non-authenticated attacker from the Internet.

Expected Remediation Time​

⌚ 60 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: N
  • Integrity: N
  • Availability: N

Temporal​

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

Result​

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

Code Examples​

Compliant code​

Correctly configure the signing keys before building the apk

android {
  signingConfigs {
    getByName("config") {
      keyAlias = keystoreProperties["keyAlias"]
      keyPassword = keystoreProperties["keyPassword"]
      storeFile = file(keystoreProperties["storeFile"])
      storePassword = keystoreProperties["storePassword"]
    }
  }
  ...
}

Non compliant code​

Unconfigured signing keys for the apk

android {
  signingConfigs {
    getByName("config") {
      empty
    }
  }
  ...
}

Requirements​