Sensitive information in source code - API Key
Description
The encryption key is stored in the source code in plain text and is not obtained from a secure source that guarantees its confidentiality.
Impact
- Generate an elaborate brute-force attack on the applications encrypted messages.
- Open easily information of a company, web and API security to sensitive data exposure.
Recommendation
It is recommended to load encryption keys from:
- A key vault service.
- A configuration file that is properly encrypted.
- Administrative environment variables.
Threat
Unauthorized user obtaining the encryption key directly from the application repository or an application file.
Expected Remediation Time
⌚ 45 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: N
- Availability: N
Temporal
- Exploit code maturity: P
- Remediation level: O
- Report confidence: C
Result
- Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C
- Score:
- Severity:
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): N
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
Result 4.0
- Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
- Score:
- Severity:
Requirements
Fixes
Free trial