Summary
Github Token Leak in aegir
Affected versions of aegir bundle and publish the current users github token to npm when aegir-release is executed.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Update to version 12.0.8 or later.
If you used this module to do a release for your project you should invalidate the GitHub tokens that were leaked.
Frequently Asked Questions
- What is CVE-2017-16225? CVE-2017-16225 is a high-severity security vulnerability in aegir (npm), affecting versions >= 12.0.0, <= 12.0.7. It is fixed in 12.0.8.
- Which versions of aegir are affected by CVE-2017-16225? aegir (npm) versions >= 12.0.0, <= 12.0.7 is affected.
- Is there a fix for CVE-2017-16225? Yes. CVE-2017-16225 is fixed in 12.0.8. Upgrade to this version or later.
- Is CVE-2017-16225 exploitable, and should I be worried? Whether CVE-2017-16225 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2017-16225 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2017-16225? Upgrade
aegirto 12.0.8 or later.