Sensitive information in source code - Git history

Description

Sensitive information such as usernames, service credentials or access tokens can be found in the git history.

Impact

Obtain sensitive information to compromise more resources or services.

Recommendation

• Remove the sensitive information from the Git history.
• Change the compromised access credentials.

Threat

Authenticated user from Internet with access to the source code.

Expected Remediation Time

⌚ minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the src.

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: U
• 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:U/RC:C
• Score:
  • Base: 4.3
  • Temporal: 4.1
• Severity:
  • Base: Medium
  • Temporal: Medium

Requirements

• 145.Protect system cryptographic keys
• 156.Source code without sensitive information
• 266.Disable insecure functionalities

Fixes

• Python

free trial

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.