CVE-2019-10347 json
Stored credentials unencrypted in Jenkins Mashup Portlets Plugin
published 7y ago modified 4mo ago also GHSA-9p5v-6p5f-f28h , EUVD-2022-3417
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Jenkins Mashup Portlets Plugin stored credentials unencrypted on the Jenkins master where they can be viewed by users with access to the master file system.
Patch / fix
- maven javagh.jenkins:mashup-portlets-plugin 1.1.0
Is CVE-2019-10347 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
1.81% chance of exploitation in the next 30 days, higher than 78% 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 | javagh.jenkins:mashup-portlets-plugin | <1.1.0 |
1.1.0 |
Affected products
- Jenkins project Jenkins Mashup Portlets Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/mashup-portlets-plugin/commit/05eb9bfd5c758c8c477ce6bd4315fd65d83e9a0a
web
-
jenkins.io
/security/advisory/2019-07-11/#SECURITY-775
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/07/11/4
mailing-list, web, third-party-advisory
-
securityfocus.com
/bid/109156
vdb-entry, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10347
advisory
Sources
- CVE List CVE-2019-10347
- GitHub Advisory GHSA-9p5v-6p5f-f28h
- NVD CVE-2019-10347
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.