Skip to content

Support bundles can include user session IDs in Jenkins Support Core Plugin

Low severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Dec 15, 2023

Package

maven org.jenkins-ci.plugins:support-core (Maven)

Affected versions

<= 2.72

Patched versions

2.72.1

Description

Support Core Plugin 2.72 and earlier provides the serialized user authentication as part of the "About user (basic authentication details only)" information (user.md).

In some configurations, this can include the session ID of the user creating the support bundle. Attackers with access to support bundle content and the Jenkins instance could use this information to impersonate the user who created the support bundle.
Support Core Plugin 2.72.1 no longer provides the serialized user authentication as part of the "About user (basic authentication details only)" information.

As a workaround, deselecting "About user (basic authentication details only)" before creating a support bundle will exclude the affected information from the bundle.

References

Published by the National Vulnerability Database Feb 24, 2021
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 13, 2022
Last updated Dec 15, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

EPSS score

0.084%
(36th percentile)

Weaknesses

CVE ID

CVE-2021-21621

GHSA ID

GHSA-92pg-8g57-hqpx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.