CVE-2019-10348 json
Jenkins Gogs Plugin stored credentials in plain text
published 7y ago modified 4mo ago also GHSA-q736-rgcp-q443 , EUVD-2022-4906
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Jenkins Gogs Plugin stored 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 org.jenkins-ci.plugins:gogs-webhook 1.0.15
Is CVE-2019-10348 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.65% chance of exploitation in the next 30 days, higher than 76% 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.0 | 4.3 | CVSS:3.0/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:gogs-webhook | <1.0.15 |
1.0.15 |
Affected products
- Jenkins project Jenkins Gogs Plugin
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
github.com
/jenkinsci/gogs-webhook-plugin/commit/34de11fe0822864c4c340b395dadebca8cb11844
web
-
jenkins.io
/security/advisory/2019-07-11/#SECURITY-1438
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/07/11/4
mailing-list, web, third-party-advisory
-
securityfocus.com
/bid/109156
vdb-entry, third-party-advisory
-
zerodayinitiative.com
/advisories/ZDI-19-837/
third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2019-10348
advisory
Sources
- CVE List CVE-2019-10348
- GitHub Advisory GHSA-q736-rgcp-q443
- NVD CVE-2019-10348
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.