dbcve.org
Convert To PipelineApplication · Jenkins

CVE-2023-28676

HIGH · 8.8 CVSS v3.1 Published 2023-04-02
Fix available
A fix is available. Upgrade to after 1.0 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 Convert To Pipeline Plugin 1.0 and earlier allows attackers to create a Pipeline based on a Freestyle project, potentially leading to remote code execution (RCE).

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 Convert To Pipeline Plugin versions 1.0 and earlier contains a CSRF vulnerability that allows authenticated attackers to trick users into creating Pipeline projects from existing Freestyle projects. Since Jenkins Pipelines can execute arbitrary build scripts and commands, this CSRF vector can lead to remote code execution on the Jenkins master or connected agents.

MitigationUpdate the Jenkins Convert To Pipeline Plugin to the latest version once available, or disable the plugin until a patch is released. Ensure Jenkins global CSRF protection is enabled as a defense-in-depth measure.

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
Convert To PipelineApplication
Affected:<= 1.0

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 if Convert To Pipeline plugin is installed
    Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins. Look for 'Convert To Pipeline' in the installed plugins list. Alternatively, check the plugin manifest file in the jenkins_home/plugins directory.
    Affected if The plugin appears in the installed plugins list and is enabled
  2. Check the installed version of Convert To Pipeline plugin
    In Manage Jenkins > Manage Plugins > Installed, find the Convert To Pipeline plugin and note the version number displayed in the version column.
    Affected if The version is 1.0 or any version earlier than 1.0 (e.g., 0.x, 0.9, etc.)
  3. Confirm the plugin status is active
    In the plugin management interface, verify that the Convert To Pipeline plugin shows as 'Enabled' or 'Active' rather than disabled or pending restart.
    Affected if The plugin is enabled and actively loaded by Jenkins
  4. Verify global CSRF protection is enabled
    Navigate to Manage Jenkins > Configure Global Security. Under the 'CSRF Protection' section, confirm that the default protection checkbox is enabled or that a CSRF crumb issuer is configured.
    Affected if CSRF protection is disabled (this indicates a defense-in-depth control is missing, increasing the impact of the vulnerability)

You are affected if the Convert To Pipeline plugin is installed at version 1.0 or earlier and is currently enabled 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.0
Interim mitigation

Update the Jenkins Convert To Pipeline Plugin to the latest version once available, or disable the plugin until a patch is released. Ensure Jenkins global CSRF protection is enabled as a defense-in-depth measure.

Recommended fix Moderate confidence

Convert To Pipeline Plugin 1.1 or later

  1. Navigate to 'Manage Jenkins' > 'Manage Plugins' > 'Installed' tab
  2. Locate the 'Convert To Pipeline' plugin in the list
  3. Check the current version is 1.0 or earlier
  4. If an update is available, select the plugin and click 'Update'
  5. After updating, restart Jenkins or wait for the plugin to reload
  6. Verify the new version is installed by checking the plugin details

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

Fix this in Convert To Pipeline 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-2023-28676 — 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-28676 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