{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-compute-engine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16546 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:google-compute-engine to 4.2.0 or later.","what":"CVE-2019-16546 is a medium-severity vulnerability in Jenkins Google Compute Engine Plugin, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16546 and fix it if it is affected.\n\nWhat it is: CVE-2019-16546 is a medium-severity vulnerability in Jenkins Google Compute Engine Plugin, published on 21 Nov 2019. 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-2019-16546 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:google-compute-engine (Maven): affected all versions; fixed in 4.2.0\n- org.jenkins-ci.plugins:google-compute-engine (Maven): affected all versions; fixed in 4.2.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-2019-16546/ (Markdown: https://insights.sbomify.com/CVE-2019-16546/index.md)","id":"CVE-2019-16546","markdown":"https://insights.sbomify.com/CVE-2019-16546/index.md","name":"CVE-2019-16546","record":{"aliases":["GHSA-345p-pw5q-g98v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GCE Plugin","requires_auth":"none","summary":"Jenkins Google Compute Engine Plugin fails to verify SSH host keys, allowing man-in-the-middle attacks against agent connections.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"google_compute_engine","vendor":"jenkins"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Jenkins Google Compute Engine Plugin 4.1.1 and earlier does not verify SSH host keys when connecting agents created by the plugin, enabling man-in-the-middle attacks.","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 Google Compute Engine Plugin does not verify SSH host keys when connecting agents created by the plugin","id":"CVE-2019-16546","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Google Compute Engine Plugin Missing Authorization vulnerability","id":"CVE-2019-16547"},"packages":[{"ecosystem":"Maven","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-compute-engine","purl":null,"source":"GHSA-345p-pw5q-g98v"},{"ecosystem":"Maven","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-compute-engine","purl":"pkg:maven/org.jenkins-ci.plugins/google-compute-engine","source":"GHSA-345p-pw5q-g98v"}],"prev":{"headline":"Jenkins QMetry for JIRA Plugin shows plain text password in configuration form","id":"CVE-2019-16545"},"products":["Jenkins Google Compute Engine Plugin"],"published":"2019-11-21","related":[{"cvss_score":8.8,"headline":"Jenkins NeuVector Vulnerability Scanner Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2023-49673","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":8.8,"headline":"Jenkins Google Compute Engine Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2019-16548","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":4.3,"headline":"Private key stored in plain text by Jenkins Google Compute Engine Plugin","id":"CVE-2022-29052","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":4.3,"headline":"Jenkins Google Compute Engine Plugin Missing Authorization vulnerability","id":"CVE-2019-16547","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":2.7,"headline":"Jenkins Google Compute Engine Plugin has incorrect permission checks","id":"CVE-2023-49652","kev_date_added":null,"published":"2023-11-29"}],"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-05","vendors":["Jenkins project"]},"summary":"Jenkins Google Compute Engine Plugin fails to verify SSH host keys, allowing man-in-the-middle attacks against agent connections.","url":"https://insights.sbomify.com/CVE-2019-16546/"}