Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:rapiddeploy-jenkins

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. High, CVSS 7.6MavenPublished

    XXE vulnerability in Jenkins RapidDeploy Plugin

    CVE-2020-2171 · GHSA-g7w4-r4mg-gvhx

    Affected
    • Maven org.jenkins-ci.plugins:rapiddeploy-jenkins < 4.2.1
    Fixed in
    4.2.1· Vendor fix available
    Issue
    RapidDeploy Plugin 4.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. This allows a user able to control the input files for the 'RapidDeploy deployment package build' build or post-build step to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller, server-side request forgery, or denial-of-service attacks. RapidDeploy Plugin 4.2.1 disables external entity resolution for its XML parser.

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

    Stored XSS vulnerability in Jenkins RapidDeploy Plugin

    CVE-2020-2170 · GHSA-f4gq-7hvf-fjm3

    Affected
    • Maven org.jenkins-ci.plugins:rapiddeploy-jenkins < 4.2.1
    Fixed in
    4.2.1· Vendor fix available
    Issue
    RapidDeploy Plugin 4.2 and earlier does not escape package names in its displayed table of packages obtained from a remote server. This results in a stored cross-site scripting (XSS) vulnerability exploitable by users able to configure jobs. RapidDeploy Plugin 4.2.1 escapes package names.

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