CVE-2016-10526

Published May 31, 2018 CVSS 3.0 · 8.6 High EPSS 1.6% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD 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 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
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Sep 16, 2024, 8:37 PM
Reserved
Oct 29, 2017, 12:00 AM
Status
Modified
Published
May 31, 2018, 8:29 PM
Modified
Jun 17, 2026, 12:39 AM