{"answers":{"affected":"2 open source packages ship an affected version, including com.bmuschko:gradle-vagrant-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21361 in the wild and no public exploit code.","fix":"Upgrade com.bmuschko:gradle-vagrant-plugin to 3.0.0 or later.","what":"CVE-2021-21361 is a medium-severity vulnerability in JLLeitschuh security-research, published on 9 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21361 and fix it if it is affected.\n\nWhat it is: CVE-2021-21361 is a medium-severity vulnerability in JLLeitschuh security-research, published on 9 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21361 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.bmuschko:gradle-vagrant-plugin (Maven): affected from 0.6; fixed in 3.0.0\n- com.bmuschko:gradle-vagrant-plugin (Maven): affected from 0.6; fixed in 3.0.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-2021-21361/ (Markdown: https://insights.sbomify.com/CVE-2021-21361/index.md)","id":"CVE-2021-21361","markdown":"https://insights.sbomify.com/CVE-2021-21361/index.md","name":"CVE-2021-21361","record":{"aliases":["GHSA-jpcm-4485-69p7"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gradle Vagrant plugin","requires_auth":"none","summary":"The Gradle Vagrant plugin logs system environment variables, potentially exposing sensitive credentials in public CI/CD logs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vagrant","vendor":"vagrant_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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. This is fixed in version 3.0.0.","ecosystems":["Maven"],"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":"Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin","id":"CVE-2021-21361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":2,"n_references":4,"next":{"headline":"Bypassing readOnly policy by creating a temporary 'mc share upload' URL","id":"CVE-2021-21362"},"packages":[{"ecosystem":"Maven","fixed":["3.0.0"],"introduced":["0.6"],"last_affected":[],"package":"com.bmuschko:gradle-vagrant-plugin","purl":null,"source":"GHSA-jpcm-4485-69p7"},{"ecosystem":"Maven","fixed":["3.0.0"],"introduced":["0.6"],"last_affected":[],"package":"com.bmuschko:gradle-vagrant-plugin","purl":"pkg:maven/com.bmuschko/gradle-vagrant-plugin","source":"GHSA-jpcm-4485-69p7"}],"prev":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Products.GenericSetup","id":"CVE-2021-21360"},"products":["security-research"],"published":"2021-03-09","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-08-03","vendors":["JLLeitschuh"]},"summary":"The Gradle Vagrant plugin logs system environment variables, potentially exposing sensitive credentials in public CI/CD logs.","url":"https://insights.sbomify.com/CVE-2021-21361/"}