What is the severity of CVE-2023-50772?

CVE-2023-50772 is considered a high severity vulnerability due to the exposure of access tokens in Jenkins configuration files.

How do I fix CVE-2023-50772?

To fix CVE-2023-50772, upgrade the Jenkins Dingding JSON Pusher Plugin to version 2.1 or later, which addresses the unencrypted storage of access tokens.

Who is affected by CVE-2023-50772?

Users of Jenkins Dingding JSON Pusher Plugin version 2.0 and earlier are affected by CVE-2023-50772.

What impact does CVE-2023-50772 have on Jenkins security?

CVE-2023-50772 poses a risk by allowing unauthorized users with Item/Extended Read permission to view sensitive access tokens.

Is there a workaround for CVE-2023-50772?

As a temporary workaround for CVE-2023-50772, users can restrict access to the Jenkins controller file system and limit permissions for users to mitigate exposure.

Vulnerability/
CVE-2023-50772

medium

4.3

CWE

312

13/12/2023

2/12/2024

CVE-2023-50772

First published: Wed Dec 13 2023(Updated: )

Jenkins Dingding JSON Pusher Plugin 2.0 and earlier stores access tokens unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

Credit: jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
maven/com.zintow:dingding-json-pusher	<=2.0
Jenkins Dingding-Notifications	<=2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-50772?
CVE-2023-50772 is considered a high severity vulnerability due to the exposure of access tokens in Jenkins configuration files.
How do I fix CVE-2023-50772?
To fix CVE-2023-50772, upgrade the Jenkins Dingding JSON Pusher Plugin to version 2.1 or later, which addresses the unencrypted storage of access tokens.
Who is affected by CVE-2023-50772?
Users of Jenkins Dingding JSON Pusher Plugin version 2.0 and earlier are affected by CVE-2023-50772.
What impact does CVE-2023-50772 have on Jenkins security?
CVE-2023-50772 poses a risk by allowing unauthorized users with Item/Extended Read permission to view sensitive access tokens.
Is there a workaround for CVE-2023-50772?
As a temporary workaround for CVE-2023-50772, users can restrict access to the Jenkins controller file system and limit permissions for users to mitigate exposure.

collector/github-advisory-latest
alias/GHSA-wjr6-v4c7-8cv6
alias/CVE-2023-50772
collector/github-advisory
agent/references
agent/type
agent/first-publish-date
agent/weakness
agent/severity
agent/description
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/trending
agent/source
agent/author
agent/softwarecombine
agent/tags
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-cve
package-manager/maven
vendor/jenkins
canonical/jenkins dingding-notifications
version/jenkins dingding-notifications/2.0

Company

Resources

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.