CVE-2019-16545 json
Jenkins QMetry for JIRA Plugin shows plain text password in configuration form
published 6y ago modified 4mo ago also GHSA-793w-q2h5-8h5j , EUVD-2022-2958
- cvss
- 6.5
- 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 45%
- public exploits
- 0
- none known
Summary
Jenkins QMetry for JIRA - Test Management Plugin transmits credentials in its configuration in plain text as part of job configuration forms, potentially resulting in their exposure.
Patch / fix
- maven org.jenkins-ci.plugins:qmetry-for-jira-test-management 1.14.0
Is CVE-2019-16545 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 FencerExploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% 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 |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 3.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:qmetry-for-jira-test-management | <1.14.0 |
1.14.0 |
Affected products
- Jenkins project Jenkins QMetry for JIRA - Test Management Plugin
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
github.com
/jenkinsci/qmetry-for-jira-test-management-plugin/commit/6711f566b72c099f10b1cecab406786ca998651d
web
- jenkins.io /security/advisory/2019-11-21/#SECURITY-727%20%282%29
-
openwall.com
/lists/oss-security/2019/11/21/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-16545
advisory
-
jenkins.io
/security/advisory/2019-11-21/#SECURITY-727%20(2)
web
Sources
- CVE List CVE-2019-16545
- GitHub Advisory GHSA-793w-q2h5-8h5j
- NVD CVE-2019-16545
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.