A cross-site request forgery (CSRF) vulnerability in Jenkins NeuVector Vulnerability Scanner Plugin 1.22 and earlier allows attackers to connect to an attacker-specified hostname and port using attacker-specified username and password.
Product
jenkins google compute engine vulnerabilities
6 published CVES affecting jenkins google compute engine, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 2
- Medium
- 3
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest jenkins google compute engine CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.45%
-
LowCVSS 2.7 EPSS 0.53%
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 s...
-
MediumCVSS 4.3 EPSS 0.75%
Jenkins Google Compute Engine Plugin 4.3.8 and earlier stores private keys unencrypted in cloud agent config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.
-
CVE-2019-16548 Jenkins Google Compute Engine Plugin Cross-Site Request Forgery vulnerability
PublishedHighCVSS 8.8 EPSS 0.86%A cross-site request forgery vulnerability in Jenkins Google Compute Engine Plugin 4.1.1 and earlier in ComputeEngineCloud#doProvision could be used to provision new agents.
-
MediumCVSS 5.9 EPSS 0.87%
Jenkins Google Compute Engine Plugin 4.1.1 and earlier does not verify SSH host keys when connecting agents created by the plugin, enabling man-in-the-middle attacks.
-
MediumCVSS 4.3 EPSS 0.69%
Missing permission checks in various API endpoints in Jenkins Google Compute Engine Plugin 4.1.1 and earlier allow attackers with Overall/Read permission to obtain limited information about the plugin configuration and environment.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.