CVE-2019-10461 json
Jenkins Dynatrace Plugin vulnerable to Insufficiently Protected Credentials
published 7y ago modified 4mo ago also GHSA-6xw9-qq9h-cr68 , EUVD-2022-2881
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
Jenkins Dynatrace Application Monitoring Plugin 2.1.3 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:dynatrace-dashboard 2.1.4
Is CVE-2019-10461 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.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/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:dynatrace-dashboard | <2.1.4 |
2.1.4 |
Affected products
- Jenkins project Jenkins Dynatrace Application Monitoring Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
jenkins.io
/security/advisory/2019-10-23/#SECURITY-1477
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/10/23/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10461
advisory
-
github.com
/jenkinsci/dynatrace-plugin
package
Sources
- CVE List CVE-2019-10461
- GitHub Advisory GHSA-6xw9-qq9h-cr68
- NVD CVE-2019-10461
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.