Vulnerability in com.bmuschko:gradle-vagrant-plugin (CVE-2021-21361)
Summary
Vulnerability in com.bmuschko:gradle-vagrant-plugin (CVE-2021-21361). Confidential information can be exposed externally. Mitigation: upgrade to 3.0.0 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21361 has been found in com.bmuschko:gradle-vagrant-plugin.
Confidential information can be exposed externally.
What to do: upgrade com.bmuschko:gradle-vagrant-plugin to 3.0.0 or later.
If unsure, ask your IT team or search "com.bmuschko:gradle-vagrant-plugin CVE-2021-21361" on the vendor's site.
CVE-2021-21361 (com.bmuschko:gradle-vagrant-plugin) — CWE-532
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 3.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in com.bmuschko:gradle-vagrant-plugin.
Check the vendor advisory for the affected versions of com.bmuschko:gradle-vagrant-plugin.
Severity: ?. Confidential information can be exposed externally.
Update to 3.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.bmuschko:gradle-vagrant-plugin を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.bmuschko:gradle-vagrant-plugin to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com