Sensitive information in source code

Description

The source code repository contains sensitive information such as usernames, passwords, email addresses and IP addresses, among others. Alternatively, while values may be password=123 o aws.secret_key=test, they reveal the bad practice of storing sensitive information in the repository with no encryption, and sooner or later they can be replaced for real sensitive values.

Impact

Get sensitive information or private secrets.

Recommendation

- Delete all hardcoded sensitive information.
- Change all affected access credentials.
- Remove sensitive information from git logs.
- Load sensitive data from safe sources such as, key vault services, configuration files properly encrypted or administrative environment variables.

Threat

Anonymous attacker with access to the source-code from the Internet.

Expected Remediation Time

⌚ 30 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: H
Remediation level: U
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:H/RL:U/RC:C
Score:

Base: 3.7
Temporal: 3.7

Severity:

Base: Low
Temporal: Low

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): N
Integrity (VI): N
Availability (VA): N
Confidentiality (SC): L
Integrity (SI): N
Availability (SA): N

Threat 4.0

Exploit maturity: U

Result 4.0

Vector string: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:U
Score:

CVSS-BT: 1.3

Severity:

CVSS-BT: Low

Details

Why

When secret credentials are compromised, we always generate a vulnerability report either the credentials are mocks, or are functional only in specific scenarios such as local environments. The risk of this scenario is usually considered in the severity tab. For local environment credentials the risk is low but not zero.

Hence to solve this vulnerability we recommend to remove the credentials from the source code, change the compromised credentials and ideally remove the credentials from the git log. In some cases the last recommendation cannot be applied to avoid traceability issues. If that's the case, in addition to removing the credentials from the code, we require a customer confirmation that the credentials were changed to close the vulnerability.

Requirements

Fixes

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.