CVE-2019-10416: Violation comments to gitlab Violation Comments To GitLab Plugin Vulnerability

MODERATE
Advisory Identifier: GHSA-3p8r-p4q5-mc44
Share
CVSS 4.3
CWE-522
Published
Advisory Summary

CVE-2019-10416 is a MODERATE (CVSS 4.3) violation comments to gitlab plugin vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Violation comments to gitlab libraries in the Maven ecosystem. The issue involves violation comments to gitlab plugin has insufficiently protected credentials. Remediation is available by upgrading affected packages to version 2.29.

CVE-2019-10416 at a Glance

CVE Identifier CVE-2019-10416
GHSA Identifier GHSA-3p8r-p4q5-mc44
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Violation comments to gitlab
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2019-10416

To remediate this vulnerability, upgrade all affected Violation comments to gitlab dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.jenkins-ci.plugins:violation-comments-to-gitlab fixed: 2.29 
<dependency>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>violation-comments-to-gitlab</artifactId>
    <version>2.29</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2019-10416, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins

Analyze the terminal output to locate any version of Violation comments to gitlab in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.29), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.jenkins-ci.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Violation comments to gitlab, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2019-10416 Affected Violation comments to gitlab Versions

1 component(s)
Fixed Versions:
2.29
Product / Package Ecosystem Affected Versions Fixed Version
org.jenkins-ci.plugins:violation-comments-to-gitlab
maven/org.jenkins-ci.plugins/violation-comments-to-gitlab
Maven
< 2.29
2.29

References

NVD — CVE-2019-10416 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-10416
Security Fix Commit FIX COMMIT
https://github.com/jenkinsci/violation-comments-to-gitlab-plugin/commit/e8237a803012bae7773d8bd10fe02e21892be3fe
Violation comments to gitlab Security Information SECURITY
https://jenkins.io/security/advisory/2019-09-25/#SECURITY-1577
Violation comments to gitlab Security Information SECURITY
http://www.openwall.com/lists/oss-security/2019/09/25/3

Frequently Asked Questions

What is CVE-2019-10416?
CVE-2019-10416 is a security vulnerability in Violation comments to gitlab involving Violation Comments to GitLab Plugin has Insufficiently Protected Credentials under CWE-522: Insufficiently Protected Credentials.
Which Violation comments to gitlab versions are affected?
Affected versions include releases prior to 2.29 across affected packages: org.jenkins-ci.plugins:violation-comments-to-gitlab.
What version fixes CVE-2019-10416?
Upgrading to 2.29 (or the latest patched release for your respective branch) resolves the vulnerability.
Is violation-comments-to-gitlab affected?
Yes, org.jenkins-ci.plugins:violation-comments-to-gitlab is affected in releases prior to 2.29. Upgrade your dependency to 2.29 or later.
What is the CVSS score of CVE-2019-10416?
CVE-2019-10416 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2019-10416?
CVE-2019-10416 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check Maven dependencies for CVE-2019-10416?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.jenkins-ci.plugins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3p8r-p4q5-mc44",
  "modified" : "2023-02-23T20:31:42Z",
  "published" : "2022-05-24T16:56:46Z",
  "aliases" : [ "CVE-2019-10416" ],
  "summary" : "Violation Comments to GitLab Plugin has Insufficiently Protected Credentials",
  "details" : "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.\n\nViolation 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.jenkins-ci.plugins:violation-comments-to-gitlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.29"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-10416"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jenkinsci/violation-comments-to-gitlab-plugin/commit/e8237a803012bae7773d8bd10fe02e21892be3fe"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2019-09-25/#SECURITY-1577"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2019/09/25/3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-522" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-02-23T20:31:42Z",
    "nvd_published_at" : "2019-09-25T16:15:00Z"
  }
}