{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:elasticsearch-query. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34807 is a medium-severity vulnerability in Jenkins Elasticsearch Query Plugin, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34807 and fix it if it is affected.\n\nWhat it is: CVE-2022-34807 is a medium-severity vulnerability in Jenkins Elasticsearch Query Plugin, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-34807 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:elasticsearch-query (Maven): affected all versions up to 1.2; no fix listed\n- org.jenkins-ci.plugins:elasticsearch-query (Maven): affected all versions up to 1.2; no fix listed\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-2022-34807/ (Markdown: https://insights.sbomify.com/CVE-2022-34807/index.md)","id":"CVE-2022-34807","markdown":"https://insights.sbomify.com/CVE-2022-34807/index.md","name":"CVE-2022-34807","record":{"aliases":["GHSA-h5h5-m2mc-j2pv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Elasticsearch Plugin","requires_auth":"low_privilege","summary":"Attackers with file system access can read unencrypted passwords from the Jenkins Elasticsearch Query Plugin configuration file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"elasticsearch_query","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Elasticsearch Query Plugin 1.2 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.","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":false,"headline":"Plaintext Storage of a Password in Jenkins Elasticsearch Query Plugin","id":"CVE-2022-34807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Token stored in plain text by Jenkins Cisco Spark Plugin","id":"CVE-2022-34808"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2"],"package":"org.jenkins-ci.plugins:elasticsearch-query","purl":null,"source":"GHSA-h5h5-m2mc-j2pv"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2"],"package":"org.jenkins-ci.plugins:elasticsearch-query","purl":"pkg:maven/org.jenkins-ci.plugins/elasticsearch-query","source":"GHSA-h5h5-m2mc-j2pv"}],"prev":{"headline":"Plaintext Storage of a Password in Jenkins Jigomerge Plugin","id":"CVE-2022-34806"},"products":["Jenkins Elasticsearch Query Plugin"],"published":"2022-06-30","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":["Jenkins project"]},"summary":"Attackers with file system access can read unencrypted passwords from the Jenkins Elasticsearch Query Plugin configuration file.","url":"https://insights.sbomify.com/CVE-2022-34807/"}