CVE-2020-2103: Infoleak

Published Jan 29, 2020
·
Updated

Jenkins 2.218 and earlier, LTS 2.204.1 and earlier exposed session identifiers on a user's detail object in the whoAmI diagnostic page.

Other sources

Jenkins shows various technical details about the current user on the /whoAmI page. In a previous fix, the Cookie header value containing the HTTP session ID was redacted. However, user metadata shown on this page could also include the HTTP session ID in Jenkins 2.218 and earlier, LTS 2.204.1 and earlier.

This allows attackers able to exploit a cross-site scripting vulnerability to obtain the HTTP session ID value from this page.

Jenkins 2.219, LTS 2.204.2 no longer prints out the affected user metadata that might contain the HTTP session ID.

Additionally, we also redact values of further authentication-related HTTP headers in addition to Cookie on this page as a hardening.

Affected Software

4 affected componentsFixes available
maven/org.jenkins-ci.main:jenkins-core<2.204.2
2.204.2
maven/org.jenkins-ci.main:jenkins-core>=2.205<2.219
2.219
Jenkins Jenkins<=2.204.1
Jenkins Jenkins<=2.218

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.204.2
  2. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.219
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.219
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.204.2
  5. Configuration

    Apply the hardening/redaction so that authentication-related HTTP header values (including the `Cookie` header value containing the HTTP session ID) are redacted on the Jenkins `/whoAmI` page; this was introduced/covered in the previous fix for `Cookie` in the SECURITY-1505 advisory.

    Jenkins /whoAmI diagnostic page Redaction of authentication-related HTTP header values (including Cookie) = Redact HTTP session identifier from authentication-related headers

Event History

Jan 29, 2020
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
05:07 PM

Frequently Asked Questions

1

What is the severity of CVE-2020-2103?

CVE-2020-2103 is classified as a medium severity vulnerability.

2

How do I fix CVE-2020-2103?

To fix CVE-2020-2103, upgrade Jenkins to version 2.204.2 or 2.219 or later.

3

What versions of Jenkins are affected by CVE-2020-2103?

Jenkins versions 2.218 and earlier, as well as LTS versions 2.204.1 and earlier are affected by CVE-2020-2103.

4

What does CVE-2020-2103 expose?

CVE-2020-2103 exposes session identifiers on the user's detail object in the whoAmI diagnostic page.

5

Is there a workaround for CVE-2020-2103?

There is no documented workaround for CVE-2020-2103; updating to a secure version is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203