Quick answers
- Is CVE-2020-7654 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-7654 being exploited in the wild.
- How severe is CVE-2020-7654?
- Low severity, with a CVSS score of 3.1, published 3 June 2020.
- Which products and versions are affected?
- snyk-broker (npm) SEMVER:introduced=0,fixed=4.73.1; Snyk Broker before 4.73.1.
- Is there a fix for CVE-2020-7654?
- Yes. snyk-broker (npm): upgrade to 4.73.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-7654 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2020-7654?
- Check whether you run snyk-broker (npm) or Snyk Broker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- snyk-broker (npm): upgrade to 4.73.1 or later
npm install snyk-broker@4.73.1
Technical details
The vulnerability is an information exposure issue (CWE-532) in the Snyk Broker application where private keys are logged when the application logging level is set to DEBUG. The vulnerable component is the logging system, which fails to redact or suppress sensitive authentication credentials. An attacker with access to application logs (local file access, centralized logging systems, or container logs) can extract private keys used for authentication. The attack vector is local and does not require network access or user interaction. Versions before 4.73.1 are affected; the fix is to upgrade to version 4.73.1 or later, which implements proper log sanitization.
Affected products
- Snyk Broker before 4.73.1
Identifiers
- CVE-2020-7654
- GHSA-mgh5-4h95-qj4p
Timeline
- 2020-05-28: disclosed
- 2020-06-03: advisory
- 2020-06-03: patched: Version 4.73.1 released with fix