Skip to content
Fencer Intel
high 8.8

CVE-2019-10302 json

Jenkins jira-ext Plugin stores credentials unencrypted

published 7y ago modified 4mo ago also GHSA-chm8-wp3h-f4m3 , EUVD-2022-3583

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

Summary

Jenkins jira-ext Plugin 0.8 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.

Patch / fix

  • maven org.jenkins-ci.plugins:jira-ext 0.9

Is CVE-2019-10302 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

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

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:jira-ext
<0.9
0.9

Affected products

  • Jenkins project Jenkins jira-ext Plugin

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-256 Plaintext Storage of a Password

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.