{"answers":{"affected":"5 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core and jenkins. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34174 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.332.4 or 2.356.","what":"CVE-2022-34174 is a high-severity vulnerability in Jenkins Jenkins, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34174 and fix it if it is affected.\n\nWhat it is: CVE-2022-34174 is a high-severity vulnerability in Jenkins Jenkins, published on 22 Jun 2022. 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-2022-34174 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.332.4\n- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.332.4\n- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.334; fixed in 2.356\n- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.334; fixed in 2.356\n- jenkins (Bitnami): affected all versions; fixed in 2.355.1\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-34174/ (Markdown: https://insights.sbomify.com/CVE-2022-34174/index.md)","id":"CVE-2022-34174","markdown":"https://insights.sbomify.com/CVE-2022-34174/index.md","name":"CVE-2022-34174","record":{"aliases":["BIT-jenkins-2022-34174","GHSA-9grj-j43m-mjqr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins automation server","requires_auth":"none","summary":"Attackers can enumerate valid usernames via timing differences on the login form, facilitating targeted credential attacks against Jenkins instances.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"jenkins","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","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-203","name":"Observable Discrepancy"}],"description":"In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username, and login attempts with a valid username and wrong password, when using the Jenkins user database security realm.","ecosystems":["Bitnami","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":"Observable timing discrepancy allows determining username validity in Jenkins","id":"CVE-2022-34174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"jenkins:jenkins","products":["jenkins:jenkins"],"type":"information_disclosure","year":"2022"},"n_packages":5,"n_references":1,"next":{"headline":"Unauthorized view fragment access in Jenkins","id":"CVE-2022-34175"},"packages":[{"ecosystem":"Bitnami","fixed":["2.355.1"],"introduced":["0"],"last_affected":[],"package":"jenkins","purl":"pkg:bitnami/jenkins","source":"BIT-jenkins-2022-34174"},{"ecosystem":"Maven","fixed":["2.332.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":null,"source":"GHSA-9grj-j43m-mjqr"},{"ecosystem":"Maven","fixed":["2.332.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":"pkg:maven/org.jenkins-ci.main/jenkins-core","source":"GHSA-9grj-j43m-mjqr"},{"ecosystem":"Maven","fixed":["2.356"],"introduced":["2.334"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":null,"source":"GHSA-9grj-j43m-mjqr"},{"ecosystem":"Maven","fixed":["2.356"],"introduced":["2.334"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":"pkg:maven/org.jenkins-ci.main/jenkins-core","source":"GHSA-9grj-j43m-mjqr"}],"prev":{"headline":"Cross-site Scripting vulnerability in Jenkins","id":"CVE-2022-34173"},"products":["Jenkins"],"published":"2022-06-22","related":[{"cvss_score":9.8,"headline":"Jenkins Command Line Interface (CLI) Path Traversal","id":"CVE-2024-23897","kev_date_added":"2024-08-19","published":"2024-01-24"},{"cvss_score":9.8,"headline":"Jenkins Stapler Web Framework Deserialization of Untrusted Data","id":"CVE-2018-1000861","kev_date_added":"2022-02-10","published":"2018-12-10"},{"cvss_score":9.8,"headline":"Jenkins Remote Code Execution","id":"CVE-2017-1000353","kev_date_added":"2025-10-02","published":"2018-01-29"},{"cvss_score":7.5,"headline":"Jenkins User Interface (UI) Information Disclosure","id":"CVE-2015-5317","kev_date_added":"2023-05-12","published":"2015-11-25"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21690","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21691","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21692","kev_date_added":null,"published":"2021-11-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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 can enumerate valid usernames via timing differences on the login form, facilitating targeted credential attacks against Jenkins instances.","url":"https://insights.sbomify.com/CVE-2022-34174/"}