-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
1841696
commit 98b6d68
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
title: Usage of Insecure Signature Key Size | ||
platform: android | ||
id: MASTG-TEST-0x39-2 | ||
type: [static] | ||
weakness: MASWE-0104 | ||
--- | ||
|
||
## Overview | ||
|
||
For Android apps, the cryptographic strength of the APK signature is essential for maintaining the app's integrity and authenticity. Using a signature key with insufficient length, such as an RSA key shorter than 2048 bits, weakens security, making it easier for attackers to compromise the signature. This vulnerability could allow malicious actors to forge signatures, tamper with the app's code, or distribute unauthorized, modified versions. | ||
|
||
## Steps | ||
|
||
1. List the additional signature information using @MASTG-TECH-0116. | ||
|
||
## Observation | ||
|
||
The output should contain the information about the key size in a line like: `Signer #1 key size (bits):`. | ||
|
||
## Evaluation | ||
|
||
The test case fails if any of the key sizes (in bits) is less than 2048 (RSA). For example, `Signer #1 key size (bits): 1024`. |