Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:violation-comments-to-gitlab

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

    Jenkins Violation Comments to GitLab Plugin has Insufficiently Protected Credentials

    CVE-2019-10415 · GHSA-8hwr-589g-xpj2

    Affected
    • Maven org.jenkins-ci.plugins:violation-comments-to-gitlab < 2.29
    Fixed in
    2.29· Vendor fix available
    Issue
    Violation Comments to GitLab Plugin stored API tokens unencrypted in job config.xml files and its global configuration file org.jenkinsci.plugins.jvctgl.ViolationsToGitLabGlobalConfiguration.xml on the Jenkins controller. These credentials could be viewed by users with Extended Read permission, or access to the Jenkins controller file system. Violation Comments to GitLab Plugin now stores these credentials encrypted. Existing jobs need to have their configuration saved for existing plain text credentials to be overwritten.

    Recommended action: Upgrade to 2.29 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 4.3MavenPublished

    Violation Comments to GitLab Plugin has Insufficiently Protected Credentials

    CVE-2019-10416 · GHSA-3p8r-p4q5-mc44

    Affected
    • Maven org.jenkins-ci.plugins:violation-comments-to-gitlab < 2.29
    Fixed in
    2.29· Vendor fix available
    Issue
    Violation Comments to GitLab Plugin stored API tokens unencrypted in job config.xml files and its global configuration file org.jenkinsci.plugins.jvctgl.ViolationsToGitLabGlobalConfiguration.xml on the Jenkins controller. These credentials could be viewed by users with Extended Read permission, or access to the Jenkins controller file system. Violation Comments to GitLab Plugin now stores these credentials encrypted. Existing jobs need to have their configuration saved for existing plain text credentials to be overwritten.

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