dbcve.org
Beaker BuilderApplication · Jenkins

CVE-2022-34207

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.10 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins Beaker builder Plugin 1.10 and earlier allows attackers to connect to an attacker-specified URL.

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 confidence

This is a CSRF vulnerability in the Jenkins Beaker builder Plugin version 1.10 and earlier. Attackers can exploit this to trick authenticated Jenkins users into unknowingly triggering the plugin to make connections to attacker-specified URLs, potentially enabling further attacks such as data exfiltration or proxying malicious requests through the Jenkins server.

MitigationUpgrade to Beaker builder Plugin version 1.11 or later, which includes proper CSRF protection (crumb token validation) on the affected endpoints. If upgrading is not immediately possible, consider restricting user permissions and monitoring for suspicious outbound connections.

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
Beaker BuilderApplication
Affected:<= 1.10

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Beaker Builder plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Beaker Builder' in the list of installed plugins
    Affected if The Beaker Builder plugin appears in the installed plugins list
  2. Check installed Beaker Builder version
    In the Installed plugins tab, locate Beaker Builder and note the version number displayed in the Version column
    Affected if The version is 1.10 or earlier (compare your version to the affected range: <= 1.10)
  3. Verify plugin is configured and active
    Go to Jenkins > Manage Jenkins > Configure System and look for Beaker Builder configuration section; also check if any jobs reference Beaker Builder
    Affected if The plugin has an active configuration or is used in job definitions, making the CSRF vulnerability exploitable
  4. Audit for unexpected outbound connections
    Review Jenkins system logs and network logs for any connections from Jenkins to unfamiliar or suspicious URLs that could indicate exploitation of the CSRF flaw
    Affected if There are outbound connections to unknown external URLs that were not intentionally configured

You are affected if the Beaker Builder plugin version is 1.10 or earlier AND the plugin is installed and active in your Jenkins environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.10
Interim mitigation

Upgrade to Beaker builder Plugin version 1.11 or later, which includes proper CSRF protection (crumb token validation) on the affected endpoints. If upgrading is not immediately possible, consider restricting user permissions and monitoring for suspicious outbound connections.

Recommended fix High confidence

Beaker Builder Plugin version 1.11

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the Beaker Builder plugin in the list
  5. If version 1.10 or earlier is installed, click 'Update' to upgrade to the fixed version
  6. Alternatively, download the Beaker Builder plugin version 1.11 from the Jenkins plugin repository and manually upload it via 'Advanced' > 'Upload Plugin'
  7. Restart Jenkins if required for the update to take effect

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beaker Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34207 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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