grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file
Versions of `grunt-gh-pages` prior to 0.10.0 are affected by a vulnerability which may cause unencrypted GitHub credentials to be written to a log file in certain circumstances. In the `grunt-gh-pages` deployment scenario where authentication is performed by injecting a GitHub token directly into the auth portion of the URL, `grunt-gh-pages` will write the token to a log file, unencrypted. ## Recommendation Update to version 0.10.0 or later.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-10526US | high8.6 | — | ||
A common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to use it directly in the auth part of the url. In module versions < 0.9… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/tschaub/grunt-gh-pagesPACKAGE
- https://github.com/tschaub/grunt-gh-pages/commit/2d277e3e969ccd4c2d493f3795400fa77e6b6342WEB
- https://github.com/tschaub/grunt-gh-pages/pull/41WEB
- https://github.com/tschaub/grunt-gh-pages/pull/41/commits/590f69767203d8c379fe18cded93bd5ad6cb53cbWEB
- https://nvd.nist.gov/vuln/detail/CVE-2016-10526ADVISORY
- https://www.npmjs.com/advisories/85WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan