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.
References
Link | Resource |
---|---|
https://github.com/tschaub/grunt-gh-pages/pull/41 | Third Party Advisory |
https://nodesecurity.io/advisories/85 | Third Party Advisory |
https://github.com/tschaub/grunt-gh-pages/pull/41 | Third Party Advisory |
https://nodesecurity.io/advisories/85 | Third Party Advisory |
Configurations
History
21 Nov 2024, 02:44
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/tschaub/grunt-gh-pages/pull/41 - Third Party Advisory | |
References | () https://nodesecurity.io/advisories/85 - Third Party Advisory |
Information
Published : 2018-05-31 20:29
Updated : 2024-11-21 02:44
NVD link : CVE-2016-10526
Mitre link : CVE-2016-10526
CVE.ORG link : CVE-2016-10526
JSON object : View
Products Affected
grunt-gh-pages_project
- grunt-gh-pages