Skip to content

dbt-core's secret env vars written to package-lock.json in plaintext

Low severity GitHub Reviewed Published Dec 8, 2023 in dbt-labs/dbt-core • Updated Dec 8, 2023

Package

pip dbt-core (pip)

Affected versions

>= 1.7.0, < 1.7.3

Patched versions

1.7.3

Description

Impact

When used to pull source code from a private repository using a Personal Access Token (PAT), some versions of dbt-core write a URL with the PAT in plaintext to the package-lock.yml file.

Patches

The bug has been fixed in dbt-core v1.7.3.

Mitigations

Remove any git URLs with plaintext secrets from package-lock.yml file(s) on servers, workstations, or in source control. Rotate any tokens that have been written to version-controlled files.

References

@jtcohen6 jtcohen6 published to dbt-labs/dbt-core Dec 8, 2023
Published to the GitHub Advisory Database Dec 8, 2023
Reviewed Dec 8, 2023
Last updated Dec 8, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-j4g3-3q8x-jxqp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.