CVE-2020-2162

Jenkins 2.227 and earlier, LTS 2.204.5 and earlier served files uploaded as file parameters to a build without specifying appropriate Content-Security-Policy HTTP headers. This resulted in a stored cross-site scripting (XSS) vulnerability exploitable by users with permissions to build a job with file parameters.\n\nJenkins now sets Content-Security-Policy HTTP headers when serving files uploaded via a file parameter to the same value as used for files in workspaces and archived artifacts not served using the Resource Root URL.\n\nThe system property hudson.model.DirectoryBrowserSupport.CSP can be set to override the value of Content-Security-Policy headers sent when serving these files. This is the same system property used for files in workspaces and archived artifacts unless those are served via the Resource Root URL and works the same way for file parameters. See Configuring Content Security Policy to learn more.\n\nEven when Jenkins is configured to serve files in workspaces and archived artifacts using the Resource Root URL (introduced in Jenkins 2.200), file parameters are not, and therefore still subject to Content-Security-Policy restrictions.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2020-2162 has a CVSS score of 5.4 (Medium). 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.228); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2020-2162? CVE-2020-2162 is a medium-severity cross-site scripting (XSS) vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions <= 2.204.5. It is fixed in 2.228. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2020-2162? CVE-2020-2162 has a CVSS score of 5.4 (Medium). 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-2020-2162? org.jenkins-ci.main:jenkins-core (maven) versions <= 2.204.5 is affected.
4. Is there a fix for CVE-2020-2162? Yes. CVE-2020-2162 is fixed in 2.228. Upgrade to this version or later.
5. Is CVE-2020-2162 exploitable, and should I be worried? Whether CVE-2020-2162 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-2020-2162 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-2020-2162?
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.228 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.228 or later

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