{"answers":{"affected":"2 open source packages ship an affected version, including grunt-gh-pages. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10526 in the wild and no public exploit code.","fix":"Upgrade grunt-gh-pages to 0.10.0 or later.","what":"CVE-2016-10526 is a high-severity vulnerability in HackerOne grunt-gh-pages node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-10526 and fix it if it is affected.\n\nWhat it is: CVE-2016-10526 is a high-severity vulnerability in HackerOne grunt-gh-pages node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-10526 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- grunt-gh-pages (npm): affected all versions; fixed in 0.10.0\n- grunt-gh-pages (npm): affected all versions; fixed in 0.10.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2016-10526/ (Markdown: https://insights.sbomify.com/CVE-2016-10526/index.md)","id":"CVE-2016-10526","markdown":"https://insights.sbomify.com/CVE-2016-10526/index.md","name":"CVE-2016-10526","record":{"aliases":["GHSA-rrj3-qmh8-72pf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Grunt gh-pages plugin","requires_auth":"none","summary":"The plugin logs GitHub tokens to the console, potentially exposing credentials to attackers if CI logs are public.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"grunt-gh-pages","vendor":"grunt-gh-pages_project"}],"cvss":{"score":8.6,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-255","name":null},{"id":"CWE-391","name":"DEPRECATED: Unchecked Error Condition"}],"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 \u003c 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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file","id":"CVE-2016-10526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":2,"n_references":2,"next":{"headline":"Regular Expression Denial of Service in riot-compiler","id":"CVE-2016-10527"},"packages":[{"ecosystem":"npm","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"grunt-gh-pages","purl":null,"source":"GHSA-rrj3-qmh8-72pf"},{"ecosystem":"npm","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"grunt-gh-pages","purl":"pkg:npm/grunt-gh-pages","source":"GHSA-rrj3-qmh8-72pf"}],"prev":{"headline":"Authentication Bypass in hapi-auth-jwt2","id":"CVE-2016-10525"},"products":["grunt-gh-pages node module"],"published":"2018-05-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["HackerOne"]},"summary":"The plugin logs GitHub tokens to the console, potentially exposing credentials to attackers if CI logs are public.","url":"https://insights.sbomify.com/CVE-2016-10526/"}