Google Compute EngineApplication · Jenkins
CVE-2019-16548
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA CSRF vulnerability in Jenkins Google Compute Engine Plugin 4.1.1 and earlier allows attackers to trigger the ComputeEngineCloud#doProvision function without proper validation, enabling unauthorized provisioning of compute agents. This could lead to resource exhaustion, unexpected cloud costs, and potential attack surface expansion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Google Compute EngineApplication
< 4.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Google Compute Engine Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for google-compute-engine folderAffected if The plugin folder exists in plugins directory or is listed in Manage Plugins
-
Identify the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, find 'Google Compute Engine' and note the version number shownAffected if Version is 4.1.1 or earlier (versions prior to 4.2.0)
-
Verify if Cloud Compute provisioning is configuredNavigate to Jenkins > Manage Jenkins > Configure Clouds > Google Compute Engine, or check the configuration XML at JENKINS_HOME/org.jenkinsci.plugins.googlecomputeengine.GoogleComputeEngineCloud.xmlAffected if A Google Compute Engine cloud configuration exists with valid credentials and at least one configured template or instance configuration
-
Confirm the provisioning endpoint is accessibleCheck if the Jenkins CLI or API can access the provisioning endpoint, or verify the plugin's web.xml confirms the ComputeEngineCloud#doProvision URL pattern is exposed without CSRF crumb validationAffected if The plugin is installed and a cloud configuration exists, meaning the vulnerable provisioning endpoint is active
User is affected if the Google Compute Engine Plugin version is 4.1.1 or earlier AND a cloud configuration with compute engine credentials is actively defined in Jenkins.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.2.0
Upgrade to Google Compute Engine Plugin version 4.1.2 or later, which includes proper CSRF protection (crumb) implementation for the provisioning endpoint.
Fix this in Google Compute Engine
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-16548 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data