Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 21 October 2019.

Which products and versions are affected?

renovate (npm) SEMVER:introduced=13.87.0,fixed=19.38.7.

Is there a fix for This vulnerability?

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

How is This vulnerability attacked?

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

Check whether you run renovate (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.

Renovate temporary repository token leakage in Pull Request comments

Severity: low · CVSS 3.1 · Published 2019-10-21

Renovate, a popular automated dependency update tool, leaked temporary repository authentication tokens into public Pull Request comments during failures when processing Go Modules. An attacker who gains access to a Pull Request could obtain these tokens and use them to access private repositories or perform unauthorized actions, potentially compromising supply chain security and repository data.

Technologies: renovate (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 21 October 2019.
Which products and versions are affected?: renovate (npm) SEMVER:introduced=13.87.0,fixed=19.38.7.
Is there a fix for This vulnerability?: Yes. renovate (npm): upgrade to 19.38.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run renovate (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

renovate (npm): upgrade to 19.38.7 or later
```
npm install renovate@19.38.7
```

Technical details

The vulnerability is an information exposure (CWE-200) where temporary repository tokens were accidentally written into Pull Request comments during Go Modules update failure scenarios. The affected versions are 13.87.0 through 19.38.6; the defect was introduced in version 13.87.0 and fixed in version 19.38.7. The attack vector is network-based with no authentication or user interaction required. An attacker monitoring Pull Requests or having repository access could extract leaked tokens from PR comments and reuse them. Patched versions 19.38.7 and later address this issue; users can also mitigate by disabling Go Modules support.

Affected products

Renovate Renovate 13.87.0 through 19.38.6

Timeline

2019-10-18: disclosed: Published to GitHub Advisory Database on 2019-10-21
2019-10-18: patched: Fix released in version 19.38.7

References

https://github.com/renovatebot/renovate/security/advisories/GHSA-v7x3-7hw7-pcjg

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