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

⌚ minutes.

Score

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

Base

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

Temporal

• Exploit code madurity: P
• Remediation level: O
• Report confidence: C

Result

• Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C
• Score:
  • Base: 3.7
  • Temporal: 3.4
• Severity:
  • Base: Low
  • Temporal: Low

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

• 122.Validate credential ownership
• 173.Discard unsafe inputs
• 178.Use digital signatures
• 320.Avoid client-side control enforcement

Fixes

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.