Is CVE-2020-7651 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-7651 being exploited in the wild.

How severe is CVE-2020-7651?

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.79.0.

Is there a fix for CVE-2020-7651?

Yes. snyk-broker (npm): upgrade to 4.79.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-7651 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2020-7651?

Check whether you run snyk-broker (npm) 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.

CVE-2020-7651: Snyk Broker arbitrary file read via patch history

CVE-2020-7651 · Severity: low · CVSS 3.1 · Published 2020-06-03

Snyk Broker is a tool that securely proxies connections between Snyk's cloud service and on-premise Git repositories and Jira. A vulnerability in versions before 4.79.0 allows authenticated users with access to Snyk's internal network to read arbitrary files on the broker through the GitHub Commits API patch history endpoint. This could expose sensitive configuration files or credentials stored on systems running the broker.

Technologies: snyk-broker (npm). Vendors: npm.

Quick answers

Is CVE-2020-7651 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-7651 being exploited in the wild.
How severe is CVE-2020-7651?: 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.79.0.
Is there a fix for CVE-2020-7651?: Yes. snyk-broker (npm): upgrade to 4.79.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-7651 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2020-7651?: Check whether you run snyk-broker (npm) 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.79.0 or later
```
npm install snyk-broker@4.79.0
```

Technical details

The vulnerability is a path traversal issue (CWE-22) in Snyk Broker's handling of GitHub Commits API responses. The vulnerable component fails to properly sanitize patch history data returned from GitHub, allowing an authenticated attacker with network access to Snyk's internal infrastructure to construct requests that read arbitrary files on the broker system. The attack requires authentication and internal network access, limiting exposure to trusted users or those who have breached the internal network perimeter. An attacker can achieve partial file reads of sensitive files, potentially obtaining configuration data or credentials. The vulnerability was patched in version 4.79.0.

Affected products

Snyk snyk-broker before 4.79.0

Identifiers

CVE-2020-7651
GHSA-45hw-29x7-9x95

Timeline

2020-05-28: disclosed
2020-06-03: advisory
2020-06-03: patched: Version 4.79.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.