dbcve.org
Pipeline Restful ApiApplication · Jenkins

CVE-2023-37957

HIGH · 8.8 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 0.11 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Pipeline restFul API Plugin 0.11 and earlier allows attackers to connect to an attacker-specified URL, capturing a newly generated JCLI token.

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 Pipeline restFul API Plugin (versions 0.11 and earlier). Attackers can trick authenticated users into making requests to attacker-specified URLs, which allows capture of newly generated JCLI tokens. This enables session hijacking by tricking users into inadvertently exposing their authentication tokens.

MitigationUpdate the Jenkins Pipeline restFul API Plugin to version 0.12 or later, which includes proper CSRF token validation. Alternatively, disable the plugin if not needed until an update can be applied.

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
Pipeline Restful ApiApplication
Affected:<= 0.11

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
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 checks

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

  1. Verify the Pipeline Restful Api plugin is installed
    List the contents of the Jenkins plugins directory (typically $JENKINS_HOME/plugins/) and look for a file named pipeline-restful-api or similar, or check via Jenkins Script Console: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'pipeline-restful-api' }
    Affected if The plugin appears in the plugin list
  2. Determine the installed plugin version
    Check the plugin's manifest file (META-INF/MANIFEST.MF) within the plugin's .jpi/.hpi file, or run in Script Console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'pipeline-restful-api' }.version
    Affected if The version is 0.11 or earlier
  3. Confirm the plugin is enabled and active
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed, or query via Script Console: Jenkins.instance.getPlugin('pipeline-restful-api')?.enabled
    Affected if The plugin is installed and shows as enabled
  4. Verify the JCLI token functionality is accessible
    Check if the plugin's REST endpoints are reachable by accessing a typical path like /plugin/pipeline-restful-api/api/ or by reviewing the plugin's registered URL bindings via Script Console: Jenkins.instance.getExtensionList('...'). Note: The exact endpoint path depends on plugin configuration.
    Affected if The plugin is loaded and its API endpoints are registered and accessible to authenticated users

You are affected if the Pipeline Restful Api plugin is installed, enabled, and the version is 0.11 or earlier, since this allows authenticated users to be tricked via CSRF into generating tokens that can be captured.

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 0.11
Interim mitigation

Update the Jenkins Pipeline restFul API Plugin to version 0.12 or later, which includes proper CSRF token validation. Alternatively, disable the plugin if not needed until an update can be applied.

Recommended fix Moderate confidence

Version 0.12 or later (check Jenkins Plugin Site for latest available release)

  1. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  2. Locate the 'Pipeline Restful API' plugin in the list
  3. Check the installed version - if version 0.11 or earlier, an upgrade is required
  4. Select the plugin and click 'Update' or install any available newer version
  5. Restart Jenkins if required to complete the installation
  6. Verify the new version is installed and the plugin is functioning correctly

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

Fix this in Pipeline Restful Api Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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