dbcve.org
Convert To PipelineApplication · Jenkins

CVE-2023-28677

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-02
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Jenkins Convert To Pipeline Plugin 1.0 and earlier uses basic string concatenation to convert Freestyle projects' Build Environment, Build Steps, and Post-build Actions to the equivalent Pipeline step invocations, allowing attackers able to configure Freestyle projects to prepare a crafted configuration that injects Pipeline script code into the (unsandboxed) Pipeline resulting from a convertion by Jenkins Convert To Pipeline Plugin.

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 uses unsafe string concatenation to convert Freestyle project configurations (Build Environment, Build Steps, Post-build Actions) into Pipeline step invocations. An attacker with permission to configure Freestyle projects can inject malicious Pipeline script through crafted configuration fields. Because the resulting Pipeline is unsandboxed, the injected code executes with full privileges, enabling remote code execution.

MitigationUpdate the Jenkins Convert To Pipeline Plugin to a patched version when available. Until then, restrict permission to configure Freestyle projects to trusted users only and audit existing projects for suspicious configurations.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Convert To Pipeline plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Convert To Pipeline' or check the plugin version in the plugin's details panel
    Affected if The plugin appears in the installed list with version 1.0 or earlier
  2. Confirm Freestyle project type exists
    View the Jenkins dashboard and check if any Freestyle projects are listed, or use the Jenkins CLI/API: GET /api/json?tree=jobs[name,type]
    Affected if One or more Freestyle projects exist in the Jenkins instance
  3. Check user permissions for Freestyle project configuration
    Navigate to Manage Jenkins > Manage Users and review who has the 'Overall/Administer' or 'Job/Configure' permissions. Also check any project-based authorization strategies.
    Affected if Users beyond trusted administrators have permission to configure Freestyle projects
  4. Audit Freestyle project configurations for suspicious content
    Review each Freestyle project's configuration, particularly Build Environment, Build Steps, and Post-build Actions fields. Use Jenkins CLI: GET /job/{project-name}/config.xml to export and inspect configurations.
    Affected if Any Freestyle project contains unusually long strings, pipeline syntax, or unexpected script content in configuration fields that could indicate injection attempts
  5. Check for recent conversion activity
    Review Jenkins build history and console output for recent uses of the Convert To Pipeline functionality. Check /job/{project-name}/lastBuild/consoleOutput for unsandboxed script execution patterns.
    Affected if Recent conversions exist and the resulting pipeline runs without sandbox restrictions

The environment is affected if the Convert To Pipeline plugin version 1.0 or earlier is installed AND Freestyle projects exist AND untrusted users have permission to configure those projects.

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 a patched version when available. Until then, restrict permission to configure Freestyle projects to trusted users only and audit existing projects for suspicious configurations.

Recommended fix High confidence

Convert To Pipeline plugin version 1.1 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab
  3. Locate 'Convert To Pipeline' plugin in the list
  4. If an update is available, select the plugin and click 'Download now and install after restart'
  5. After update completes, verify the plugin version is 1.1 or higher
  6. Alternatively, download the .hpi file from Jenkins plugin repository (https://plugins.jenkins.io/) and upload via 'Advanced' > 'Upload Plugin'

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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