dbcve.org
KatalonApplication · Jenkins

CVE-2022-43416

HIGH · 8.8 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 1.0.33 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
Jenkins Katalon Plugin 1.0.32 and earlier implements an agent/controller message that does not limit where it can be executed and allows invoking Katalon with configurable arguments, allowing attackers able to control agent processes to invoke Katalon on the Jenkins controller with attacker-controlled version, install location, and arguments, and attackers additionally able to create files on the Jenkins controller (e.g., attackers with Item/Configure permission could archive artifacts) to invoke arbitrary OS commands.

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 Katalon Plugin before version 1.0.32 allows unsandboxed execution of Katalon with attacker-controllable arguments (version, install location, arguments). Attackers with control over agent processes can invoke Katalon on the controller with malicious parameters, while attackers with file creation privileges (e.g., Item/Configure permission) can achieve arbitrary OS command execution.

MitigationUpgrade Jenkins Katalon Plugin to version 1.0.33 or later. If upgrade is not immediately possible, restrict agent process control permissions and remove Item/Configure permissions from untrusted users until the patch 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
KatalonApplication
Affected:< 1.0.33

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. Check Jenkins Katalon Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Katalon Plugin in the list, or query the plugin via Jenkins CLI: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i katalon
    Affected if The installed version is earlier than 1.0.33 or the plugin version cannot be determined (plugin is present but unversioned)
  2. Identify active Katalon plugin usage in jobs
    Search Jenkins job configurations for Katalon-related build steps: grep -r "katalon" $JENKINS_HOME/jobs/*/config.xml 2>/dev/null or use Jenkins UI to search for jobs using the Katalon plugin
    Affected if Any Jenkins job is configured to use the Katalon plugin (the plugin need not be actively running to be vulnerable, but active usage increases exposure)
  3. Review permissions for agent process control
    Navigate to Manage Jenkins > Manage and Assign Roles > Check which users or groups have the 'Connect agent' or 'Master/Agent communication' permissions, or inspect $JENKINS_HOME/config.xml for agent-related security settings
    Affected if Untrusted users or groups have permissions to control agent processes or establish agent connections to the controller
  4. Review Item/Configure permissions
    Navigate to Manage Jenkins > Manage and Assign Roles > Check role assignments for Item/Configure or Job/Configure permissions, or review individual job ACLs in $JENKINS_HOME/jobs/*/config.xml for authorization sections
    Affected if Untrusted users or groups have Item/Configure or Job/Configure permissions on any project or the overall Jenkins instance

The environment is affected if the Katalon Plugin version is earlier than 1.0.33 AND any untrusted user has either agent process control permissions or Item/Configure permissions.

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 1.0.33 or later
Fixed in 1.0.33
Interim mitigation

Upgrade Jenkins Katalon Plugin to version 1.0.33 or later. If upgrade is not immediately possible, restrict agent process control permissions and remove Item/Configure permissions from untrusted users until the patch can be applied.

Recommended fix High confidence

Katalon Plugin version 1.0.33 or later

  1. Navigate to Jenkins > Manage Jenkins > Manage Plugins
  2. Go to the 'Updates' tab
  3. Locate the Katalon Plugin in the list
  4. Select the Katalon Plugin and click 'Download now and install after restart'
  5. Wait for the plugin to download and install
  6. Restart Jenkins to complete the installation
  7. Verify the installed version is 1.0.33 or later via Manage Plugins > Installed tab

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

Fix this in Katalon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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