Skip to content
Fencer Intel
low 3.2

GHSA-j4g3-3q8x-jxqp json

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

published 2y ago modified last yr.

cvss
3.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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](https://github.com/dbt-labs/dbt-core/releases/tag/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.

Patch / fix

  • pypi dbt-core 1.7.3

Is GHSA-j4g3-3q8x-jxqp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 3.2 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi dbt-core
>=1.7.0, <1.7.3
1.7.3

Classification

Weakness
  • CWE-315 Cleartext Storage of Sensitive Information in a Cookie

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of dbt-labs/dbt published their own advisory on GitHub. Reviewed sources take precedence over it.