Insecure digital certificates

Insecure digital certificates

Description

The apk certificate was signed using the SHA1 algorithm. This algorithm is considered quite insecure, so it should not be used to sign certificates since it can be reversed in order to obtain the signing key. On the other hand, there are URLs that, just by accessing them, it is possible to download the digital certificates stored in them, thus exposing confidential information of the organization.

Impact

- Obtain the signing key of the applications certificate.
- Change the application in the appStore to a malicious one by using the obtained signing keys.

Recommendation

Sign the certificate with SHA2 or higher.

Threat

Anonymous attacker from the Internet.

Expected Remediation Time

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

Temporal

  • Exploit code maturity: P
  • Remediation level: O
  • Report confidence: X

Result

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

Score 4.0

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

Base 4.0

  • Attack vector: N
  • Attack complexity: H
  • Attack Requirements: N
  • Privileges required: N
  • User interaction: N
  • Confidentiality (VC): L
  • Integrity (VI): L
  • Availability (VA): N
  • Confidentiality (SC): N
  • Integrity (SI): N
  • Availability (SA): N

Threat 4.0

  • Exploit maturity: P

Result 4.0

  • Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
  • Score:
    • CVSS-BT: 2.9
  • Severity:
    • CVSS-BT: Low

Compliant code

The application has a secure algorithm for the certificate signature

                android {
  signingConfigs {
    getByName("config") {
      keyAlgorithm = keystoreProperties["SHA2"]
      ...
    }
  }
}

            

Non compliant code

The application has an insecure algorithm for the certificate signature

                android {
  signingConfigs {
    getByName("config") {
      keyAlgorithm = keystoreProperties["SHA1"]
      ...
    }
  }
}

            

Requirements

Fixes

Free trial message
Free trial
Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.