Skip to content
Fencer Intel
medium 6.5

CVE-2022-38663 json

Improper masking of credentials Jenkins in Git Plugin

published 4y ago modified 4mo ago also GHSA-jxmw-3gxf-fprh , EUVD-2022-6582

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

Summary

Jenkins Git Plugin 4.11.4 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log provided by the Git Username and Password (`gitUsernamePassword`) credentials binding.

Patch / fix

  • maven org.jenkins-ci.plugins:git 4.11.5
  • Jenkins project Jenkins Git Plugin 4.9.4

Is CVE-2022-38663 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-38663 updated cvss 4.3

jenkins-2-plugins/git: Improper masking of credentials in Git Plugin

  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4 jenkins-2-plugins
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 org.jenkins-ci.plugins:git
<4.11.5
4.11.5

Affected products

  • Jenkins project Jenkins Git Plugin

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

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.