PT-2022-22352 · Jenkins · Jenkins Build Notifications Plugin+1

·

CVE-2022-34800

·

Published

2022-06-30

·

Updated

2023-11-22

CVSS v2.0

4.0

Medium

VectorAV:N/AC:L/Au:S/C:P/I:N/A:N
Name of the Vulnerable Software and Affected Versions Jenkins Build Notifications Plugin versions 1.5.0 and earlier
Description The issue allows users with access to the Jenkins controller file system to view tokens stored unencrypted in the plugin's global configuration files. Specifically, multiple tokens are stored unencrypted, including the Pushover Application Token in tools.devnull.jenkins.plugins.buildnotifications.PushoverNotifier.xml, the Slack Bot Token in tools.devnull.jenkins.plugins.buildnotifications.SlackNotifier.xml, and the Telegram Bot Token in tools.devnull.jenkins.plugins.buildnotifications.TelegramNotifier.xml.
Recommendations For Jenkins Build Notifications Plugin versions 1.5.0 and earlier, consider restricting access to the Jenkins controller file system to minimize the risk of token exposure. As a temporary workaround, restrict access to the configuration files tools.devnull.jenkins.plugins.buildnotifications.PushoverNotifier.xml, tools.devnull.jenkins.plugins.buildnotifications.SlackNotifier.xml, and tools.devnull.jenkins.plugins.buildnotifications.TelegramNotifier.xml to prevent unauthorized viewing of the tokens. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Insufficiently Protected Credentials

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2022-34800
GHSA-V3R8-6VFJ-PPPF

Affected Products

Jenkins
Jenkins Build Notifications Plugin