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.
[PLANNED FOR DEPRECATION. SEE MAINTENANCE NOTES AND CONSIDER CWE-252, CWE-248, OR CWE-1069.] Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed.
Weaknesses in this category are related to the management of credentials.
Link | Tags |
---|---|
https://github.com/tschaub/grunt-gh-pages/pull/41 | third party advisory |
https://nodesecurity.io/advisories/85 | third party advisory |