CVE-2023-49652 json
Jenkins Google Compute Engine Plugin has incorrect permission checks
published 2023-11-29 2 y ago modified 2026-06-17 4 mo ago also GHSA-pgpj-83g3-mfr2 , EUVD-2023-3006
- cvss
- 2.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
Incorrect permission checks in Jenkins Google Compute Engine Plugin 4.550.vb_327fca_3db_11 and earlier allow attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate system-scoped credentials IDs of credentials stored in Jenkins and to connect to Google Cloud Platform using attacker-specified credentials IDs obtained through another method, to obtain information about existing projects. This fix has been backported to 4.3.17.1.
Patch / fix
- maven org.jenkins-ci.plugins:google-compute-engine 4.3.17.1, 4.551.v5a
- Jenkins Project Jenkins Google Compute Engine Plugin 4.551.v5a_4dc98f6962
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/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:google-compute-engine | <4.3.17.1 >=4.5, <4.551.v5a |
4.3.17.1 4.551.v5a |
Affected products
- Jenkins Project Jenkins Google Compute Engine Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
jenkins.io
/security/advisory/2023-11-29/#SECURITY-2835
vendor-advisory, web
-
openwall.com
/lists/oss-security/2023/11/29/1
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-49652
advisory
Sources
- CVE List CVE-2023-49652
- GitHub Advisory GHSA-pgpj-83g3-mfr2
- NVD CVE-2023-49652
Fencer Vulns 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.