CVE-2019-10416 Violation Comments to GitLab Plugin has Insufficiently Protected Credentials

Medium 6.5 Published Updated

Attackers with Extended Read permission or master file system access can view unencrypted GitLab credentials stored in Jenkins job configuration files.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2019-10416?

CVE-2019-10416 is a medium-severity vulnerability in Jenkins Violation Comments to GitLab Plugin, published on 25 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or access to the master file system.

Weakness: CWE-522

Which versions are affected by CVE-2019-10416?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:violation-comments-to-gitlab. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.plugins:violation-comments-to-gitlab MavenAll versions2.29
org.jenkins-ci.plugins:violation-comments-to-gitlab MavenAll versions2.29

Products include Jenkins Violation Comments to Gitlab.

How do I fix CVE-2019-10416?

Upgrade org.jenkins-ci.plugins:violation-comments-to-gitlab to 2.29 or later.

Is CVE-2019-10416 being exploited?

There is no known exploitation of CVE-2019-10416 in the wild and no public exploit code.

Sources

Also known as GHSA-3p8r-p4q5-mc44.

Is CVE-2019-10416 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free