dbcve.org
Chef SinatraApplication · Jenkins

CVE-2022-25208

HIGH · 8.8 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to after 1.20 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 missing permission check in Jenkins Chef Sinatra Plugin 1.20 and earlier allows attackers with Overall/Read permission to have Jenkins send an HTTP request to an attacker-controlled URL and have it parse an XML response.

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

The Jenkins Chef Sinatra Plugin versions 1.20 and earlier lacks a permission check in certain endpoints, allowing any user with Overall/Read permission to trigger Jenkins into sending HTTP requests to attacker-controlled URLs and parsing the XML responses. This is a Server-Side Request Forgery (SSRF) vulnerability combined with an authorization bypass.

MitigationUpgrade the Chef Sinatra Plugin to version 1.21 or later which contains the permission check fix. If immediate patching is not possible, restrict Overall/Read permission to trusted users only to reduce the attack surface.

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
Chef SinatraApplication
Affected:<= 1.20

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Verify Chef Sinatra Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Chef Sinatra' or 'chef-sinatra' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Determine installed plugin version
    In the Manage Plugins > Installed tab, locate the Chef Sinatra plugin and note the version number displayed in the 'Version' column
    Affected if The installed version is 1.20 or earlier (e.g., 1.20, 1.19, 1.18, etc.)
  3. Verify Overall/Read permission configuration
    Navigate to Jenkins > Manage Jenkins > Manage Users and/or check Configure Global Security > Authorization settings to see which users or groups have Overall/Read permission
    Affected if Users other than trusted administrators have Overall/Read permission enabled
  4. Confirm endpoint accessibility
    Attempt to access the Chef Sinatra plugin REST endpoints (typically under /plugin/chef-sinatra/) or verify via API: GET /api/json?tree=plugins[name,version]
    Affected if The plugin is active and responding to API calls

You are affected if the Chef Sinatra Plugin is installed at version 1.20 or earlier AND any untrusted user has Overall/Read permission in your Jenkins instance.

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.20
Interim mitigation

Upgrade the Chef Sinatra Plugin to version 1.21 or later which contains the permission check fix. If immediate patching is not possible, restrict Overall/Read permission to trusted users only to reduce the attack surface.

Recommended fix Moderate confidence

Chef Sinatra Plugin version 1.21 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the 'Chef Sinatra' plugin in the list
  5. Check if the current version is 1.21 or later
  6. If an earlier version is installed, click 'Update' to upgrade to the latest version
  7. Restart Jenkins if required to complete the installation

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

Fix this in Chef Sinatra Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25208 — 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-25208 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