Debian Package BuilderApplication · Jenkins
CVE-2022-23118
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 · uneditedJenkins Debian Package Builder Plugin 1.6.11 and earlier implements functionality that allows agents to invoke command-line `git` at an attacker-specified path on the controller, allowing attackers able to control agent processes to invoke arbitrary OS commands on the controller.
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 confidenceThe Jenkins Debian Package Builder Plugin versions 1.6.11 and earlier allows agent processes to specify an arbitrary filesystem path for the git executable, which is then invoked on the controller. An attacker who controls the agent (through compromised agent processes or malicious agent configurations) can specify a malicious executable path to achieve arbitrary OS command execution on the controller.
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
Debian Package BuilderApplication
<= 1.6.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Debian Package Builder Plugin is installedNavigate to Jenkins Manage Plugins > Installed and search for 'Debian Package Builder' or check the plugin directory $JENKINS_HOME/plugins for the debian-package-builder folderAffected if The plugin is present in the Jenkins instance
-
Determine the installed plugin versionIn Jenkins Manage Plugins > Installed, locate the Debian Package Builder plugin and note the version number displayedAffected if The version is 1.6.11 or earlier
-
Identify connected or configured agentsNavigate to Manage Jenkins > Manage Nodes and review all configured agents, noting any that are untrusted or from untrusted sourcesAffected if There are agents connected that are not fully trusted or whose processes could be controlled by untrusted users
-
Check for agent-accessible git configurationReview the Debian Package Builder job configurations and global configuration to see if agents can supply or modify the git executable path settingAffected if The plugin configuration allows agents to specify custom git executable paths that get executed on the controller
A user is affected if the Debian Package Builder Plugin version 1.6.11 or earlier is installed AND untrusted or compromised agents can connect to the Jenkins controller.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade the Jenkins Debian Package Builder Plugin to version 1.6.12 or later, which implements proper path validation. Until then, restrict or disable untrusted agent connections and review agent process configurations.
1.6.12 or later
- Navigate to the Jenkins dashboard
- Go to Manage Jenkins > Manage Plugins
- Click on the 'Installed' tab
- Find 'Debian Package Builder' in the list
- If the installed version is 1.6.11 or earlier, click 'Update now' to upgrade to the fixed version
- Restart Jenkins if required to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Package Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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