CVE-2019-1003037 json
Unprivileged users with Overall/Read access are able to enumerate credential IDs in Azure VM Agents Plugin
published 7y ago modified 4mo ago also GHSA-r2vw-x3hr-969v , EUVD-2022-5070
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
An information exposure vulnerability exists in Jenkins Azure VM Agents Plugin 0.8.0 and earlier in src/main/java/com/microsoft/azure/vmagent/AzureVMCloud.java that allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
Patch / fix
- maven org.jenkins-ci.plugins:azure-vm-agents 0.8.1
Is CVE-2019-1003037 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.28% chance of exploitation in the next 30 days, higher than 70% 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 | org.jenkins-ci.plugins:azure-vm-agents | <0.8.1 |
0.8.1 |
Affected products
- Jenkins project Jenkins Azure VM Agents Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/jenkinsci/azure-vm-agents-plugin/commit/e36c8a9b0a436d3b79dc14b5cb4f7f6032fedd3f
web
-
jenkins.io
/security/advisory/2019-03-06/#SECURITY-1332
web, vendor-advisory
-
securityfocus.com
/bid/107476
vdb-entry, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-1003037
advisory
-
github.com
/jenkinsci/azure-vm-agents-plugin
web
Sources
- CVE List CVE-2019-1003037
- GitHub Advisory GHSA-r2vw-x3hr-969v
- NVD CVE-2019-1003037
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.