{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:azure-keyvault. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30514 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:azure-keyvault to 188.vf46b or later.","what":"CVE-2023-30514 is a high-severity vulnerability in Jenkins Azure Key Vault Plugin, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-30514 and fix it if it is affected.\n\nWhat it is: CVE-2023-30514 is a high-severity vulnerability in Jenkins Azure Key Vault Plugin, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-30514 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:azure-keyvault (Maven): affected all versions; fixed in 188.vf46b\n- org.jenkins-ci.plugins:azure-keyvault (Maven): affected all versions; fixed in 188.vf46b\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-2023-30514/ (Markdown: https://insights.sbomify.com/CVE-2023-30514/index.md)","id":"CVE-2023-30514","markdown":"https://insights.sbomify.com/CVE-2023-30514/index.md","name":"CVE-2023-30514","record":{"aliases":["GHSA-gmxm-pr58-v5jc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Jenkins Azure Key Vault Plugin","requires_auth":"none","summary":"Attackers can view unmasked Azure Key Vault credentials in build logs when push mode for durable task logging is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"azure_key_vault","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Jenkins Azure Key Vault Plugin 187.va_cd5fecd198a_ and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.","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":"Jenkins Azure Key Vault Plugin does not properly mask credentials","id":"CVE-2023-30514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Thycotic DevOps Secrets Vault Plugin does not properly mask credentials","id":"CVE-2023-30515"},"packages":[{"ecosystem":"Maven","fixed":["188.vf46b"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-keyvault","purl":null,"source":"GHSA-gmxm-pr58-v5jc"},{"ecosystem":"Maven","fixed":["188.vf46b"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:azure-keyvault","purl":"pkg:maven/org.jenkins-ci.plugins/azure-keyvault","source":"GHSA-gmxm-pr58-v5jc"}],"prev":{"headline":"Jenkins Kubernetes Plugin does not properly mask credentials","id":"CVE-2023-30513"},"products":["Jenkins Azure Key Vault Plugin"],"published":"2023-04-12","related":[{"cvss_score":4.3,"headline":"Missing permission checks in Jenkins Azure Key Vault Plugin allow enumerating credentials IDs","id":"CVE-2020-2313","kev_date_added":null,"published":"2020-11-04"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-07","vendors":["Jenkins Project"]},"summary":"Attackers can view unmasked Azure Key Vault credentials in build logs when push mode for durable task logging is enabled.","url":"https://insights.sbomify.com/CVE-2023-30514/"}