Grunt Gh Pages Node Module
Approved changes feed: RSS · Atom
cpe:2.3:a:hackerone:grunt-gh-pages_node_module:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hackerone (9b72fff1-532f-502a-8030-14fc4a21dd17) |
|---|---|
| Product | Grunt Gh Pages Node Module (58c7375a-59e3-5cef-8bb1-0aaab8820c06) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-10526 |
vulnerable | 2026-06-08 05:07:25.261735 |
Details available
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.
Published: 2018-05-31T20:00:00.000Z
Updated: 2024-09-16T20:37:56.998Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.