Displayed in plain text by Dingding JSON Pusher Plugin

published 2023-12-13 2y ago modified 2026-06-17 4mo ago also GHSA-q5cj-xf99-79m8 , EUVD-2023-3266

cvss: 4.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

Jenkins Dingding JSON Pusher Plugin 2.0 and earlier does not mask access tokens displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

Is CVE-2023-50773 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	com.zintow:dingding-json-pusher	<=2.0	no fix listed

Affected products

Jenkins Project Jenkins Dingding JSON Pusher Plugin

Classification

Weakness

CWE-312 Cleartext Storage of Sensitive Information
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

jenkins.io /security/advisory/2023-12-13/#SECURITY-3184
vendor-advisory, web
openwall.com /lists/oss-security/2023/12/13/4
web, mailing-list
nvd.nist.gov /vuln/detail/CVE-2023-50773
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.