168 – Insecure service configuration - Keystore
Description
Cryptographic key containers such as keystores should have good security practices, among them: - The Secretkey and Keystore should be in protected environments. - The secrets should be aligned with strong password policies (do not use default passwords). - The Secretkey should not be stored in the source code. - Passwords to access the Keystore should not be the same as the private password.
Impact
Get access to the private keys of the debugging certificates to test the application and understand its operation to generate new attack vectors.
Recommendation
Implement good security practices against Keystore containers. - Do not store secrets in the source code. - Change default passwords.
Threat
Authenticated attacker from intranet.
Expected Remediation Time
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: A
- Attack complexity: H
- Attack Requirements: N
- Privileges required: L
- User interaction: N
- Confidentiality (VC): L
- Integrity (VI): N
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: P