CVE-2022-34171

Since Jenkins 2.321 and LTS 2.332.1, the HTML output generated for new symbol-based SVG icons includes the title attribute of l:ionicon until Jenkins 2.334 and alt attribute of l:icon since Jenkins 2.335 without further escaping.

This vulnerability is known to be exploitable by attackers with Job/Configure permission.

Jenkins 2.356, LTS 2.332.4 and LTS 2.346.1 addresses this vulnerability, the title attribute of l:ionicon (Jenkins LTS 2.332.4) and alt attribute of l:icon (Jenkins 2.356 and LTS 2.346.1) are escaped in the generated HTML output.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-34171 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.356, 2.346.1, 2.332.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-34171? CVE-2022-34171 is a high-severity path traversal vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 2.350, < 2.356. It is fixed in 2.356, 2.346.1, 2.332.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-34171? CVE-2022-34171 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2022-34171? org.jenkins-ci.main:jenkins-core (maven) versions >= 2.350, < 2.356 is affected.
4. Is there a fix for CVE-2022-34171? Yes. CVE-2022-34171 is fixed in 2.356, 2.346.1, 2.332.4. Upgrade to this version or later.
5. Is CVE-2022-34171 exploitable, and should I be worried? Whether CVE-2022-34171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-34171 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-34171?
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.356 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.346.1 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.332.4 or later

Other vulnerabilities in org.jenkins-ci.main:jenkins-core