Skip to content

← Public intelligence

Maven package

com.redgate.plugins.redgatesqlci:redgate-sql-ci

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 4.3MavenPublished

    Redgate SQL Change Automation Plugin stored credentials in plain text

    CVE-2020-2095 · GHSA-x23m-8c2h-6wg7

    Affected
    • Maven com.redgate.plugins.redgatesqlci:redgate-sql-ci < 2.0.5
    Fixed in
    2.0.5· Vendor fix available
    Issue
    Redgate SQL Change Automation Plugin 2.0.4 and earlier stores a NuGet API key unencrypted in job config.xml files as part of its configuration. This credential could be viewed by users with Extended Read permission or access to the Jenkins controller file system. This is due to an incomplete fix of SECURITY-1598. Redgate SQL Change Automation Plugin 2.0.5 now stores the API key encrypted. Existing jobs need to have their configuration saved for existing plain text passwords to be overwritten.

    Recommended action: Upgrade to 2.0.5 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 6.5MavenPublished

    Jenkins Redgate SQL Change Automation Plugin has Insufficiently Protected Credentials

    CVE-2019-16557 · GHSA-9hpq-528p-48j3

    Affected
    • Maven com.redgate.plugins.redgatesqlci:redgate-sql-ci < 2.0.4
    Fixed in
    2.0.4· Vendor fix available
    Issue
    Jenkins Redgate SQL Change Automation Plugin 2.0.3 and earlier stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.

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