CVE-2021-21361 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in com.bmuschko:gradle-vagrant-plugin. 2 public exploit references exist, so weaponization risk is real. A fix is available for com.bmuschko:gradle-vagrant-plugin — see the affected versions and patch details below.
Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-21361 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.bmuschko:gradle-vagrant-pluginReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The com.bmuschko:gradle-vagrant-plugin Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables.
When this Gradle plugin is executed in public CI/CD, this can lead to sensitive credentials being exposed to malicious actors.
Patches
Fixed in version 3.0.0
References
- https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44
- https://github.com/bmuschko/gradle-vagrant-plugin/issues/19
- https://github.com/bmuschko/gradle-vagrant-plugin/pull/20
For more information
If you have any questions or comments about this advisory:
- Open an issue in bmuschko/gradle-vagrant-plugin
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.bmuschko:gradle-vagrant-plugin | ≥ 0.6&&< 3.0.0 | 3.0.0com.bmuschko:gradle-vagrant-plugin:3.0.0 |
Affected Products
vagrantvagrant_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.bmuschko:gradle-vagrant-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.bmuschko:gradle-vagrant-plugin to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21361 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2021-21361 in your dependencies?
Find it across Maven, including transitive dependencies.