Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:katalon

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.3MavenPublished

    API keys stored in plain text by Jenkins Katalon Plugin

    CVE-2022-43419 · GHSA-35rx-7pc8-6963

    Affected
    • Maven org.jenkins-ci.plugins:katalon < 1.0.33
    Fixed in
    1.0.33· Vendor fix available
    Issue
    Jenkins Katalon Plugin 1.0.32 and earlier stores API keys unencrypted in job config.xml files on the Jenkins controller as part of its configuration. These API keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. Katalon Plugin 1.0.33 no longer stores the API keys directly, instead accessing them through its Credentials Plugin integration, once affected job configurations are saved again.

    Recommended action: Upgrade to 1.0.33 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.8MavenPublished

    Jenkins Katalon Plugin vulnerable to Protection Mechanism Failure

    CVE-2022-43416 · GHSA-q6f6-6c4p-xph4

    Affected
    • Maven org.jenkins-ci.plugins:katalon < 1.0.33
    Fixed in
    1.0.33· Vendor fix available
    Issue
    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. It allows attackers able to control agent processes to invoke Katalon on the Jenkins controller with attacker-controlled version, install location, and arguments. Attackers additionally able to create files on the Jenkins controller (e.g., attackers with Item/Configure permission could archive artifacts) can invoke arbitrary OS commands. Katalon Plugin 1.0.33 changes the message type to controller-to-agent, preventing execution on the controller.

    Recommended action: Upgrade to 1.0.33 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 4.2MavenPublished

    CSRF vulnerability in Jenkins Katalon Plugin allows capturing credentials

    CVE-2022-43418 · GHSA-x8j7-vxh9-p67g

    Affected
    • Maven org.jenkins-ci.plugins:katalon < 1.0.34
    Fixed in
    1.0.34· Vendor fix available
    Issue
    Katalon Plugin 1.0.33 and earlier does not require POST requests for several HTTP endpoints, resulting in cross-site request forgery (CSRF) vulnerabilities. This vulnerability allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. Katalon Plugin 1.0.34 requires POST requests for the affected HTTP endpoints.

    Recommended action: Upgrade to 1.0.34 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 4.2MavenPublished

    Missing permission checks in Jenkins Katalon Plugin allow capturing credentials

    CVE-2022-43417 · GHSA-5fvg-h778-jjjx

    Affected
    • Maven org.jenkins-ci.plugins:katalon < 1.0.33
    Fixed in
    1.0.33· Vendor fix available
    Issue
    Katalon Plugin 1.0.32 and earlier does not perform permission checks in several HTTP endpoints. This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. Katalon Plugin 1.0.33 properly performs permission checks when accessing the affected HTTP endpoints.

    Recommended action: Upgrade to 1.0.33 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →