ZulipApplication · Jenkins
CVE-2019-10476
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Zulip Plugin 1.1.0 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Zulip Plugin version 1.0.0 through 1.1.0 stores credentials in plaintext within the plugin's global configuration file on the Jenkins master filesystem. Users with file system access to the Jenkins master can read these unencrypted credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ZulipApplication
<= 1.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Jenkins Zulip plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or list files in $JENKINS_HOME/plugins/ directory and look for zulip pluginAffected if The Zulip plugin appears in the installed plugins list
-
Determine the installed Zulip plugin versionIn Jenkins UI, click on the Zulip plugin entry in the Installed tab to view its version, or check the plugin's manifest file at $JENKINS_HOME/plugins/zulip/META-INF/MANIFEST.MFAffected if The version is 1.0.0 through 1.1.0 (inclusive)
-
Locate the plugin's global configuration fileCheck the Jenkins configuration directory for the Zulip plugin config, typically found at $JENKINS_HOME/org.jenkinsci.plugins.zulip.xml or within the plugin's directory structureAffected if The configuration file exists on the Jenkins master filesystem
-
Inspect configuration for plaintext credentialsOpen the configuration file identified in step 3 and examine its contents for API keys, tokens, or other credential strings that appear in plaintext (not encrypted or Base64-encoded)Affected if Credentials such as Zulip API keys, emails, or stream names are visible as readable text in the configuration file
A user is affected if the Zulip plugin version is 1.1.0 or earlier AND plaintext credentials are present in the plugin's configuration file on the Jenkins master.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Jenkins Zulip Plugin version 1.2.0 or later, which encrypts credentials. Rotate any credentials that may have been exposed before the upgrade.
Fix this in Zulip
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data