Skip to content
Fencer Intel
medium 4.3

CVE-2022-34801 json

Cleartext Storage of Sensitive Information in Jenkins Build Notifications Plugin

published 4y ago modified 4mo ago also GHSA-7298-w54j-q7wm , EUVD-2022-6270

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

Summary

Jenkins Build Notifications Plugin 1.5.0 and earlier transmits tokens in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.

Is CVE-2022-34801 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.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

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
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven tools.devnull:build-notifications
<=1.5.0
 no fix listed

Affected products

  • Jenkins project Jenkins Build Notifications Plugin

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-318 Cleartext Storage of Sensitive Information in Executable

References

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.