CVE-2019-10416

CVE-2019-10416 is a medium-severity vulnerability in Jenkins Violation Comments To Gitlab with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-522.

Key facts

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.

Frequently asked questions

What is CVE-2019-10416?
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.
How severe is CVE-2019-10416?
CVE-2019-10416 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-10416 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-10416?
CVE-2019-10416 affects Jenkins Violation Comments To Gitlab. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-10416?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-10416 published?
CVE-2019-10416 was published on 2019-09-25 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Jenkins Violation Comments To Gitlab

All CVEs affecting Jenkins Violation Comments To Gitlab →

Other CWE-522 (Insufficiently Protected Credentials) vulnerabilities

Browse all CWE-522 (Insufficiently Protected Credentials) vulnerabilities →