Sensitive information in source code - Dependencies
By reversing the application dependencies, it is found that the private key has been stored in the same dependency and not in a protected environment.
Obtain the private key used to decrypt the information.
Securely configure the vulnerable service so that it can only be accessed by authorized users.
Internal attacker with access to the artifactory.
Expected Remediation Time
⌚ 60 minutes.
Default score using CVSS 3.1. It may change depending on the context of the vulnerability.
- Attack vector: A
- Attack complexity: L
- Privileges required: L
- User interaction: N
- Scope: U
- Confidentiality: H
- Integrity: N
- Availability: N
- Exploit code madurity: X
- Remediation level: X
- Report confidence: X
- Vector string: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:X/RL:X/RC:X
- Base: 5.7
- Temporal: 5.7
- Base: Medium
- Temporal: Medium
Verify that none of the dependencies imported on the application store sensitive data like private keys
Non compliant code
The code has a dependency imported which stores sensitive credentials
- 145. Protect system cryptographic keys
- 156. Source code without sensitive information
- 266. Disable insecure functionalities
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.