Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:jx-resources

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

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

  1. Medium, CVSS 5.4MavenPublished

    Jenkins JX Resources Plugin missing permission check

    CVE-2019-10339 · GHSA-xqqr-mq8x-22qx

    Affected
    • Maven org.jenkins-ci.plugins:jx-resources <= 1.0.36
    Fixed in
    1.0.37· Vendor fix available
    Issue
    Jenkins jx-resources Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified Kubernetes server and obtain information about an attacker-specified namespace. Doing so might also leak service account credentials used for the connection. Additionally, it allowed attackers to obtain the value of any attacker-specified environment variable for the Jenkins controller process. Additionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability. This form validation method now requires POST requests and Overall/Administer permissions.

    Recommended action: Upgrade to 1.0.37 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. Medium, CVSS 5.4MavenPublished

    Jenkins JX Resources Plugin cross-site request forgery vulnerability

    CVE-2019-10338 · GHSA-qww5-p626-rfpf

    Affected
    • Maven org.jenkins-ci.plugins:jx-resources <= 1.0.36
    Fixed in
    1.0.37· Vendor fix available
    Issue
    Jenkins jx-resources Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified Kubernetes server and obtain information about an attacker-specified namespace. Doing so might also leak service account credentials used for the connection. Additionally, it allowed attackers to obtain the value of any attacker-specified environment variable for the Jenkins controller process. Additionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability. This form validation method now requires POST requests and Overall/Administer permissions.

    Recommended action: Upgrade to 1.0.37 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 →