Description
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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0342 | 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. |
Github GHSA |
GHSA-rrj3-qmh8-72pf | grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file |
References
History
No history.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-09-16T20:37:56.998Z
Reserved: 2017-10-29T00:00:00.000Z
Link: CVE-2016-10526
No data.
Status : Modified
Published: 2018-05-31T20:29:00.817
Modified: 2024-11-21T02:44:12.190
Link: CVE-2016-10526
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA