Most recent entries from all

cnvd-2018-11279

EUVD-2026-172195

fkie_cve-2016-10526

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.1 the auth portion of the url is outputted as part of the grunt tasks logging function. If this output is publicly available then the credentials should be considered compromised.

GHSA-rrj3-qmh8-72pf — grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file

Affected: npm: grunt-gh-pages

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.

Most recent entries from all

cnvd-2018-11279

EUVD-2026-172195

fkie_cve-2016-10526

GHSA-rrj3-qmh8-72pf — grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file

gsd-2016-10526