{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:ec2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10364 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:ec2 to 1.44 or later.","what":"CVE-2019-10364 is a medium-severity vulnerability in Jenkins Amazon EC2 Plugin, published on 31 Jul 2019. 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-2019-10364 and fix it if it is affected.\n\nWhat it is: CVE-2019-10364 is a medium-severity vulnerability in Jenkins Amazon EC2 Plugin, published on 31 Jul 2019. 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-2019-10364 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:ec2 (Maven): affected all versions; fixed in 1.44\n- org.jenkins-ci.plugins:ec2 (Maven): affected all versions; fixed in 1.44\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-10364/ (Markdown: https://insights.sbomify.com/CVE-2019-10364/index.md)","id":"CVE-2019-10364","markdown":"https://insights.sbomify.com/CVE-2019-10364/index.md","name":"CVE-2019-10364","record":{"aliases":["GHSA-w7fv-7j46-wwrv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins EC2 Plugin","requires_auth":"low_privilege","summary":"An attacker with log access can read partial private keys from Jenkins system logs, compromising EC2 instance security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"ec2","vendor":"jenkins"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Jenkins Amazon EC2 Plugin 1.43 and earlier wrote the beginning of private keys to the Jenkins system log.","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 Amazon EC2 Plugin leaked beginning of private key in system log","id":"CVE-2019-10364","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Google Kubernetes Engine Plugin vulnerable to Exposure of Resource to Wrong Sphere","id":"CVE-2019-10365"},"packages":[{"ecosystem":"Maven","fixed":["1.44"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:ec2","purl":null,"source":"GHSA-w7fv-7j46-wwrv"},{"ecosystem":"Maven","fixed":["1.44"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:ec2","purl":"pkg:maven/org.jenkins-ci.plugins/ec2","source":"GHSA-w7fv-7j46-wwrv"}],"prev":{"headline":"Cleartext Transmission of Sensitive Information in Jenkins Configuration as Code Plugin","id":"CVE-2019-10363"},"products":["Jenkins Amazon EC2 Plugin"],"published":"2019-07-31","related":[{"cvss_score":8.8,"headline":"Arbitrary shell command execution in Jenkins EC2 Plugin","id":"CVE-2017-1000502","kev_date_added":null,"published":"2018-01-24"}],"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-04","vendors":["Jenkins project"]},"summary":"An attacker with log access can read partial private keys from Jenkins system logs, compromising EC2 instance security.","url":"https://insights.sbomify.com/CVE-2019-10364/"}