# CVE-2019-16547: Jenkins Google Compute Engine Plugin Missing Authorization vulnerability

> Attackers with read permissions can access limited plugin configuration and environment information due to missing permission checks in Jenkins Google Compute Engine Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v98h-rv7j-hf6j

## What is CVE-2019-16547?

CVE-2019-16547 is a medium-severity missing authorization vulnerability in Jenkins Google Compute Engine Plugin, published on 21 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-16547?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-compute-engine. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:google-compute-engine` | Maven | All versions | 4.2.0 |
| `org.jenkins-ci.plugins:google-compute-engine` | Maven | All versions | 4.2.0 |

Products: Jenkins Google Compute Engine.

## How do I fix CVE-2019-16547?

Upgrade org.jenkins-ci.plugins:google-compute-engine to 4.2.0 or later.

## Is CVE-2019-16547 being exploited?

There is no known exploitation of CVE-2019-16547 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Google Compute Engine Plugin

- [CVE-2023-49673](https://insights.sbomify.com/CVE-2023-49673/): Jenkins NeuVector Vulnerability Scanner Plugin Cross-Site Request Forgery vulnerability (high 8.8)
- [CVE-2019-16548](https://insights.sbomify.com/CVE-2019-16548/): Jenkins Google Compute Engine Plugin Cross-Site Request Forgery vulnerability (high 8.8)
- [CVE-2019-16546](https://insights.sbomify.com/CVE-2019-16546/): Jenkins Google Compute Engine Plugin does not verify SSH host keys when connecting agents created by the plugin (medium 5.9)
- [CVE-2022-29052](https://insights.sbomify.com/CVE-2022-29052/): Private key stored in plain text by Jenkins Google Compute Engine Plugin (medium 4.3)
- [CVE-2023-49652](https://insights.sbomify.com/CVE-2023-49652/): Jenkins Google Compute Engine Plugin has incorrect permission checks (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16547 and fix it if it is affected.

What it is: CVE-2019-16547 is a medium-severity missing authorization vulnerability in Jenkins Google Compute Engine Plugin, published on 21 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16547 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:google-compute-engine (Maven): affected all versions; fixed in 4.2.0
- org.jenkins-ci.plugins:google-compute-engine (Maven): affected all versions; fixed in 4.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-16547/ (Markdown: https://insights.sbomify.com/CVE-2019-16547/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16547
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16547
- OSV: https://osv.dev/vulnerability/CVE-2019-16547

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-16547/
Summaries are generated and may contain mistakes; the official description above is the record.