Insecure service configuration - Keys
Description
The source code repository stores cipher keys directly. Allowing an attacker with access to the source code to compromise the keys to impersonate the application or decrypt the communications between server and client.
Impact
Obtain cypher keys to craft new attack vectors.
Recommendation
Store the cipher keys in a secured Keystore.
Threat
Authenticated attacker from Internet with access to the source code.
Expected Remediation Time
⌚ 30 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: L
- User interaction: N
- Scope: U
- Confidentiality: L
- Integrity: N
- Availability: N
Temporal
- Exploit code madurity: P
- Remediation level: O
- Report confidence: C
Result
- Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C
- Score:
- Base: 4.3
- Temporal: 3.9
- Severity:
- Base: Medium
- Temporal: Low
Code Examples
Compliant code
Cipher keys are safely used as encrypted secrets in the code
public class DemoApplication {
public static void main(String[] args) {
decryptPass(password, secretKey);
}
}
Non compliant code
Cipher key directly stored on the source code
public class DemoApplication {
cipherKey = "PlainKEY"
public static void main(String[] args) {
decryptPass(password, cipherKey);
}
}
Requirements
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.