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.
Metrics
Affected Vendors & Products
| Vendors | Products |
|---|---|
| Grunt-gh-pages Project |
|
No data.
No data.
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 |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-09-16T20:37:56.998Z
Reserved: 2017-10-29T00:00:00
Link: CVE-2016-10526
Vulnrichment
No data.
NVD
Status : Modified
Published: 2018-05-31T20:29:00.817
Modified: 2024-11-21T02:44:12.190
Link: CVE-2016-10526
Redhat
No data.
OpenCVE Enrichment
No data.