Approved changes feed: RSS · Atom

cpe:2.3:a:grunt-gh-pages_project:grunt-gh-pages:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorGrunt Gh Pages Project (2cc94afa-a53d-5bc8-a0c7-62eda6710df0)
ProductGrunt Gh Pages (e7792eb8-82b8-53b8-9ffa-8f5e9ad24231)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2016-10526 vulnerable 2026-06-08 05:07:25.262405 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
Reference links
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.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.