# Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin

Advisory record · `GHSA-jpcm-4485-69p7`

- **Identifiers:** `GHSA-jpcm-4485-69p7` · `CVE-2021-21361`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 9 Mar 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Mar 2021, 00:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.bmuschko:gradle-vagrant-plugin` (Maven): affected `>=0.6, <3.0.0`; fixed in `3.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The com.bmuschko:gradle-vagrant-plugin package, versions from 0.6 before 3.0.0, logs the system environment variables, which can expose sensitive information. An attacker who can read the build logs, such as in a public CI/CD pipeline, could obtain credentials. Upgrade to version 3.0.0 or later. The source gives few details beyond this.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 68th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jpcm-4485-69p7)

## Sources

- [GitHub Advisory Database: GHSA-jpcm-4485-69p7](https://github.com/advisories/GHSA-jpcm-4485-69p7)
- [OSV: GHSA-jpcm-4485-69p7](https://osv.dev/vulnerability/GHSA-jpcm-4485-69p7)
- <https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-jpcm-4485-69p7>
- <https://nvd.nist.gov/vuln/detail/CVE-2021-21361>
- <https://github.com/bmuschko/gradle-vagrant-plugin/issues/19>
- <https://github.com/bmuschko/gradle-vagrant-plugin/pull/20>
- <https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jpcm-4485-69p7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jpcm-4485-69p7/>. Everything for agents: <https://agentprime.io/llms.txt>.
