CVE-2019-10476: Jenkins Zulip Plugin Insufficiently Protected Credentials

org.jenkins-ci.plugins:zulip Updated 02 Oct 2025

Summary

24/05/2022
Yes i
High
7.8

CVE-2019-10476: Jenkins Zulip Plugin vulnerable to Insufficiently Protected Credentials. Affects org.jenkins-ci.plugins:zulip versions < 1.1.1. Fixed in 1.1.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Jenkins Zulip Plugin is a Maven-based package that provides integration between Jenkins and the Zulip messaging platform. It allows users to send notifications and messages to Zulip streams from Jenkins jobs. The plugin is widely used in software development and continuous integration workflows.

Vulnerability Detail

The Jenkins Zulip Plugin prior to version 1.1.1 suffers from an Insufficiently Protected Credentials vulnerability. This vulnerability arises from the plugin storing credentials in an unencrypted format within its global configuration file on the Jenkins master. As a result, users with access to the Jenkins master file system can view these credentials. This can lead to unauthorized access and potential misuse of sensitive information.

How To Fix

Minimum fixed version

1.1.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to upgrade to the fixed version of the plugin as soon as possible.

Conclusion

The Jenkins Zulip Plugin prior to version 1.1.1 is vulnerable to Insufficiently Protected Credentials. This can lead to unauthorized access and potential misuse of sensitive information. Users should upgrade to version 1.1.1 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:zulip →

Share this vulnerability

FAQ

This vulnerability allows users with access to the Jenkins master file system to view unencrypted credentials stored by the Jenkins Zulip Plugin. This can lead to unauthorized access and potential misuse of sensitive information.

No, only versions prior to 1.1.1 are affected. Users should upgrade to version 1.1.1 or later to mitigate the vulnerability.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

There is no known evidence of this vulnerability being exploited in the wild. However, it is still important to upgrade to the fixed version to ensure the security of your Jenkins instance.

You can find more information about the Jenkins Zulip Plugin on the official Jenkins website or the plugin's GitHub repository.

How To Fix

Minimum fixed version

1.1.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback