CVE-2019-16557 json
Jenkins Redgate SQL Change Automation Plugin has Insufficiently Protected Credentials
published 6y ago modified 4mo ago also GHSA-9hpq-528p-48j3 , EUVD-2022-3391
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Jenkins Redgate SQL Change Automation Plugin 2.0.3 and earlier stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
Patch / fix
- maven com.redgate.plugins.redgatesqlci:redgate-sql-ci 2.0.4
Is CVE-2019-16557 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.85% chance of exploitation in the next 30 days, higher than 58% 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.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.redgate.plugins.redgatesqlci:redgate-sql-ci | <2.0.4 |
2.0.4 |
Affected products
- Jenkins project Jenkins Redgate SQL Change Automation Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/redgate-sql-ci-plugin/commit/18525ee6f01a5bc36040d40f1ff63702ce7280ac
web
-
jenkins.io
/security/advisory/2019-12-17/#SECURITY-1598
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/12/17/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-16557
advisory
Sources
- CVE List CVE-2019-16557
- GitHub Advisory GHSA-9hpq-528p-48j3
- NVD CVE-2019-16557
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.