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

⌚ 120 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 maturity: 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

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: L
• 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

Result 4.0

• Vector string: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
• Score:
  • CVSS-BT: 2.1
• Severity:
  • CVSS-BT: Low

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 Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.